PARMLIB member

The APPC address space uses the APPCPMxx member of SYS1.PARMLIB. Define IMS as a local APPC component LU that is controlled by the APPC address space.

The scheduler name is the same IMSID used in the IMSCTRL macro. When IMS identifies to APPC, it passes its IMSID as the scheduler name SCHED(IMS1) in APPC member APPCPMxxx. The following is an example of the APPCPMxx member:

LUADD
     ACBNAME(IMSLU62)
     SCHED(IMS1)
     BASE
     TPDATA(SYS1.APPCTP)
     TPLEVEL(SYSTEM)

For XRF add:

USERVAR=uservar_name ALTLU=luname

The LUADD option keywords are defined below:

ACBNAME=local LUNAME of IMS
SCHED=IMS id
BASEmandatory parameter
TPDATA(TP_Profile dataset name)
TPLEVEL(system) suggested value
USERVAR=(uservar_name)
ALTLU=(LUNAME)

Related reading: For more information on these keywords, see z/OS® MVS™ Planning: APPC/MVS Management.

Communication between VTAM® and its application programs requires an ACB (application control block) whose name must be identically defined in the SYS1.VTAMLST APPL statement and in the APPCPMxx LUADD statement ACBNAME parameter.

APPC manages the IMS ACB. When IMS identifies to APPC, APPC gives IMS the name of the APPC-managed ACB name (LUNAME). The APPC LUNAME is not defined in IMS, because IMS does not manage the ACB. The entries in the SYS1.PARMLIB member APPCPMxx include both the IMS scheduler name (IMSID) and the LUNAME ACBNAME(xxxxxxx) that ties an IMS to an LUNAME.

This ACBNAME must be different from the ACBNAME used by IMS for non-LU 6.2 terminals. APPC/MVS expects its LUs to be defined as VTAM resources so that these LUs can access the SNA network. A VTAM application program (APPL) definition macro must be coded for each APPC/MVS LU. LU 6.2 application programs are only defined to VTAM, not to IMS. The SYS1.VTAMLST member example follows:

IMSLU62 APPL ACBNAME=IMSLU62
             APPC=Y
             …