The MSGRTA macro is used to specify user application programs that exist in
the host processors of the network. The data supplied via this macro is
used to create the RCAT initialization table (RCIT) and is also used in the
creation of the SNA table via the offline SNA table generation program.
All applications that are resident in the processor being generated must be
specified. Applications that use the TPF message routing protocol (that
is, routing control parameter list (RCPL) in the message header) and are not
resident in the generated processor, but may receive messages routed from the
generated processor must also be specified. In addition, the MSGRTA
macro will identify the TPF processor IDs of attached processors to the TPF
complex being generated.
- APLIC=name
- Application name consisting of four alphanumeric characters. The
first three characters may not be TPF, CLG, LOG, NEF, or SMP.
Entries in the RCAT initialization table are automatically generated for
the following fixed and optional system applications:
- CLGx
- Where x is a TPF processor ID
- LOGI
- Log processor
- SMPx
- Where x is a TPF processor ID
SIP supports up to 256 message router application names (user plus system
names).
To use TPF/APPC support in a loosely coupled complex, you must define one
TPF/APPC service LU for every processor in the complex. For these
definitions specify:
APLIC=SVCx, where x is the processor ID
EDIT=CHDD
ASNA=APPC
APROC=x, where x is the processor ID.
Attention: An application name must be unique. Only
one MSGRTA statement may be coded per application name.
- APROC=v
- One character to identify the processor in which the application
resides. For applications resident in the generated processor, this
must be the TPF processor ID defined in the SYSID parameter of the CONFIG
macro.
The TPF processor ID specified here will either identify a processor in the
SYSID parameter of CONFIG or define a processor considered to be attached to
the TPF complex being generated.
In a loosely-coupled system an asterisk (*) should be coded as the
processor due to recovery considerations. The asterisk (*) indicates
that the application is present in all processors.
The character coded for this parameter must be in the range A-Z or
0-9.
- RES
- Specify one of the following:
- NO
- This application is not a RES0 type application.
- YES
- This application is a RES0 type application. RES0 will no longer be
included automatically by the system.
If RES=YES is coded, the other parameters should be coded as follows:
EDIT=UII1
SIGN=YES
SIMFM=YES
- Note:
- Any general reservation type application which requires the use of AAA
records must code this parameter as YES. This parameter is not
necessarily connected with the CONFIG RES= parameter.
- EDIT=name
- The four character name of the program that is to receive all messages
destined for this application. This parameter is required only for
applications which are resident in the generated processor. The first
character must be alphabetic, the remaining characters are
alphanumeric. The default name of CVVC will be assigned if this
parameter is omitted for an application that is resident in the generated
processor. By assigning this default name, the SIP Stage I process can
be allowed to complete. The user, if desired, may then modify the Stage
I output for program COHA/B (RCIT) to contain the desired program name or
rerun Stage I with the corrected MSGRTA macro.
To use the TPF/APPC package, specify:
EDIT=CHDD
ASNA=APPC, ASNA=LU62, or ASNA=LOCP
DEVTYPE=SHARED
- SIGN
- Specify one of the following:
- NO
- No sign-in required.
- YES
- A sign-in message is required by the application.
- SIMFM
- Specify one of the following:
- YES
- A simulated 4505 type terminal message format will be used for this
application for messages to or from a 3270 type terminal.
- NO
- A user format for messages.
- SMP
- Specify one of the following:
- NO
- The application is not an SMP type of application.
- YES
- The application is an SMP type of application. If specified, the
other parameters should be coded as follows:
ASNA=NO
MRECV=NO
PERM=YES
RAPPL=NO
RCPL=BASIC
SIGN=NO
SIMFM=YES
APPL=P
ALTBUF=NO
- ASNA
- Specify one of the following:
- NO
- The application will address all of its terminals (logical units) using
the LNIATA type of terminal address. A terminal control record (RCB or
AAA) will be retrieved and passed to the application program with input
messages.
- YES
- The application program will address all of its terminals (logical units)
using only the SNA resource identifier (RID). Also, no terminal control
record (RCB or AAA) is to be passed to the application with input
messages.
- LU62
- The application will communicate as a TPF/APPC LU. You must
specify EDIT=CHDD, RCPL=EXP, and DEVTYPE=SHARED when using this option.
- Note:
- It is not necessary to define remote LU62 nodes here. You can define
these using the RSC statement in the offline ACF/SNA table generation program
(OSTG). See the TPF ACF/SNA Network
Generation for details.
- APPC
- The application communicates as the default local TPF/APPC LU or a
TPF/APPC service LU. You must specify EDIT=CHDD, RCPL=EXP, and
DEVTYPE=SHARED when using this option.
- LOCP
- The application communicates as the local APPN control point (CP).
You must specify EDIT=CHDD, RCPL=EXP, APROC=*, and DEVTYPE=SHARED when using
this option. Only 1 local APPN CP can be defined.
- Note:
- This parameter must be coded as YES, LU62, or APPC when the APPL parameter is
coded as S.
- TERMRCD
- Specify one of the following:
- YES
- The terminal record will be returned to the application. This
option may be specified only for non-SNA applications (ASNA=NO).
If ASNA=NO, TERMRCD=YES is the default.
- NO
- The terminal record will not be returned to the application.
If ASNA=YES, TERMRCD=NO is the default.
- PERM
- Specify one of the following:
- NO
- This application will not be permanent.
- YES
- This application will be a permanent application when functionally added
to the RCAT (it cannot be deleted).
- MRECV=NO|YES
- This parameter defines whether this application supports SNA system
message recovery.
- RCPL=BASIC|EXP
- This parameter defines whether this application uses the basic form of the
RCPL or the expanded format.
- ALTBUF
- Defines the buffer size to be used for the application using the extended
3270 devices.
- NO
- Default buffer size for the extended 3270 LU.
- YES
- Alternate buffer size for the extended 3270 LU.
- USER=username
- This parameter is only to be coded in an MDBF system. One of the 1-
to 4-character alphanumeric names used in the SSUID1-4 parameter of the SSDEF
macro associates a particular subsystem user with an application. If
omitted, the value defaults to the first/only name given in the SSUID
parameter of the SSDEF macro.
If the system is an MDBF system, all applications must be specified in the
basic subsystem. The default user is the first/only name given in the
SSUID parameter of the basic subsystem generation.
Any users appearing in MSGRTA statements must appear in some
subsystem's SSUID parameter (SSDEF).
If SSDEF is not specified, USER defaults to the value
SSU0.
Attention: An application may only be specified for one
user. (See APLIC parameter above.)
- APPL=P|S,nnn|S,1
- This parameter indicates whether the application can act as both a primary
LU (PLU) and a secondary LU (SLU), or as only a PLU.
- P
- Defines this application as a primary logical unit only. This is
the default.
- S
- Defines this application as a secondary logical unit, where nnn is a
number defining the concurrent session limit that this SLU can participate in
with a single PLU in another domain. A maximum of 255 can be
specified. The default is 1.
The SLU name is created by concatenating the 4-character PLU name with the
CPU ID specified on the APROC parameter and with a 3-digit decimal
number.
- Note:
- If this parameter is coded as S, the ASNA parameter must be coded as YES,
LU62, or APPC.
- RQR=NO|YES
- This parameter defines whether the SNA command RQR is being supported for
SLU-P threads.
- Note:
- If this parameter is coded as YES, ASNA must be YES also.
- ASR
- Specify one of the following:
- NO
- SLU-P threads will not be resynchronized during restart.
- YES
- TPF will resynchronize SLU-P threads during restart.
- Note:
- If this parameter is coded as YES, ASNA must be YES also.
- DEVTYPE
- This parameter allows you to specify different message queues for
different applications by defining which NCB slot (0-7) in an NCB
directory record entry dynamic LU resources will use when they log on to the
application. An NCB slot contains the address of a 381-byte long-term
pool file NCB record. See TPF ACF/SNA Data
Communications Reference for more information about dynamic LU
resources, NCB directory records, and NCB slots.
- Note:
- LU resources defined using the OSTG program use the same 381-byte fixed file
NCB directory record, regardless of the application. Therefore, this
parameter does not apply to LU resources that are defined using the OSTG
program.
- SHARED
- Specifies that a dynamic LU resource will use NCB slot 0 when it logs on
to the application. Use this option if you want the application to
share the same message queue with other applications.
- Note:
- You must specify this option when you specify ASNA=LU62, APPC, or
LOCP.
- TYPE1
- Specifies that a dynamic LU resource will use NCB slot 1 when it logs on
to the application. Use this option if you want the application to have
a unique message queue.
- TYPE2
- Specifies that a dynamic LU resource will use NCB slot 2 when it logs on
to the application. Use this option if you want the application to have
a unique message queue.
- TYPE3
- Specifies that a dynamic LU resource will use NCB slot 3 when it logs on
to the application. Use this option if you want the application to have
a unique message queue.
- TYPE4
- Specifies that a dynamic LU resource will use NCB slot 4 when it logs on
to the application. Use this option if you want an application to have
a unique message queue.
- TYPE5
- Specifies that a dynamic LU resource will use NCB slot 5 when it logs on
to the application. Use this option if you want an application to have
a unique message queue.
- TYPE6
- Specifies that a dynamic LU resource will use NCB slot 6 when it logs on
to the application. Use this option if you want an application to have
a unique message queue.
- TYPE7
- Specifies that a dynamic LU resource will use NCB slot 7 when it logs on
to the application. Use this option if you want an application to have
a unique message queue.
- SAWARE=NO|YES
- This parameter defines whether secondary logical unit (SLU) threads will
have session awareness support. See TPF ACF/SNA
Data Communications Reference for more information about session
awareness support.