Verify interactive job, DFHIVPOL

The verify interactive job, DFHIVPOL, is tailored to your CICS® environment and stored in the hlq.XDFHINST library when you run the DFHISTAR job.

You can use the DFHIVPOL job to start a CICS region to try out some functions, for example:

Use the main LU transaction, CEMT. You can also use CEMT from the MVS™ system console. For information about CEMT, see CEMT - main terminal.
Use the resource definition online transaction, CEDA. For information about using CEDA, see Resource management transaction CEDA commands.
Use the sample application transaction AMNU, to access the sample VSAM file, FILEA.

You require either an IBM® 3270 Information Display System LU or a console device, or both.

If you use an IBM 3270 Information Display System LU with this IVP, you can try CEDA, CEMT, and the sample applications.

From a console device, the CEDA transaction can be used only to INSTALL resource definitions. The sample programs cannot be run from a console device.

Defining an SNA LU for the online IVP

You can define an SNA LU by using one of these methods:

Use the autoinstall facility, to avoid defining LUs to CICS explicitly before they can be used, see Autoinstalling for an SNA LU.
Define a LU explicitly in the CSD, using the DEFINE command of DFHCSDUP (the batch utility for updating the CSD), see Defining an SNA LU in the CSD.

Autoinstalling for an SNA LU

With autoinstall, the resource definitions you create using RDO can act as models or templates for many resources of the same type. You then leave CICS to match real resources with one of the models. CICS installs table entries for these real resources dynamically, as and when they are required.

When using autoinstall, be aware that when CICS processes an autoinstall request, it uses data from the SNA logmode table. Be aware of this important consideration. An autoinstall request succeeds only when the logmode data, which is passed to CICS in the BIND image, matches one of the model terminal definitions recorded in the autoinstall model table (AMT) from the CSD. Before attempting to start CICS and autoinstall a LU for this IVP, check your SNA definitions with those given in Coding entries in the z/OS Communications Server LOGON mode table. If CICS fails to match model and logmode data, you receive message DFHZC6987I.

The CSD is defined and initialized for all the IVP jobs when you run the DFHCOMDS job and includes some IBM-supplied definitions for use with autoinstall. These definitions are defined in the following groups:

DFHTERM: Model LU definitions for use with autoinstall. For example, two of the TERMINAL definitions are 3270 and LU2.
DFHTYPE: Partial LU definitions (TYPETERMs) defining common LU properties, or attributes. For example, two of the TYPETERM definitions are DFH3270 (to define a non-SNA 3270 LU) and DFHLU2E2 (to define an SNA 3270 model 2 LU). The DFHLU2E2 resource definition matches the SNA-supplied logmode SNX32702.

The DFHTERM and DFHTYPE groups are included in the CICS-defined group list called DFHLIST, which is defined in the GRPLIST operand. If the CICS-supplied definitions are not suitable for your installation, you can create additional TYPETERM and model TERMINAL definitions in the CSD, but without a LU you must do this offline, using the DFHCSDUP utility program. For information about autoinstall definitions, see Autoinstall.

Autoinstall also requires a user program to assign LU identifiers, and, if necessary, to control access to the system. When you run the online IVP, you are unlikely to have any special requirements for LU identifiers, or to control access, in which case you can use the IBM-supplied autoinstall user program, DFHZATDX. If you are using autoinstall for APPC connections and LUs, the sample autoinstall user program is called DFHZATDY.

Defining an SNA LU in the CSD

If you want to use an explicitly defined LU, rather than allow CICS to autoinstall a LU, define it offline using the DFHCSDUP utility program.

The normal way to create resource definitions in the CSD is to use the CEDA DEFINE command from a CICS main LU, but without a LU you can only do this using the DFHCSDUP utility program. For an example of a DFHCSDUP job to define an SNA LU in the CSD, see Figure 1.

Figure 1. Defining a LU by using the DFHCSDUP utility program

//DEFTERM  JOB (accounting information),MSGCLASS=A,
//         MSGLEVEL=(1,1),CLASS=A,NOTIFY=userid
//VTAMDEF  EXEC PGM=DFHCSDUP
//STEPLIB  DD DSN=CICSTS54.CICS.SDFHLOAD,DISP=SHR
//DFHCSD   DD DSN=CICSTS54.CICS.DFHCSD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
*
DEFINE TERMINAL(trmidnt)   NETNAME(vtamname)  GROUP(grpname)
       TYPETERM(name)      INSERVICE(NO)      AUTINSTMODEL(NO)
*
APPEND LIST(DFHLIST) TO(yourlist)

*
ADD GROUP(grpname) LIST(yourlist)
*
LIST   LIST(yourlist)  OBJECTS
/*
//

GROUP(name): Code a unique name for the group to which the LU resource definition is to belong.
NETNAME(name): Code the 8-character SNA name that identifies this LU to your SNA system.
TERMINAL(name): Code a unique 4-character LU identifier as the name by which CICS is to know the LU.
TO(yourlist) and LIST(yourlist): Code a unique name for yourlist. If your new group list does not include all the CICS-supplied resources as well as your own, you must specify DFHLIST and yourlist on the GRPLIST system initialization parameter of your CICS startup job.
TYPETERM(name): Specify a unique name to identify the resource definition that matches the properties of the type of LU you are using. For example, to define an SNA 3270 model 2 LU, specify the CICS-supplied TYPETERM definition DFHLU2E2.

To include the CICS-supplied list of resources in a new group list, create a new list by copying the CICS-supplied list, DFHLIST, using the APPEND command. The CICS-supplied group list, DFHLIST, is a protected group that you cannot modify. You can then add your resource definition groups to the new list. Before you run the IVP, define your new group list to CICS, by adding a system initialization override to the SYSIN data set in the DFHIVPOL job stream.

Defining the CICS APPLID to SNA

Ensure that either SNA knows the CICS application identifier (APPLID) or you change the CICS APPLID to one that is already known to your SNA system.

If you use the default APPLID (DBDCCICS), define this to SNA as described in Defining specific APPL definitions and APPL parameters to SNA, before starting the DFHIVPOL job.

Communicating with CICS from an MVS console or a TSO session

If you want to communicate with CICS from an MVS console, you must define a console in the CSD before starting the IVP. You cannot define a console in the TCT. For more information about defining consoles, see Defining console devices to CICS.

If you want to communicate with CICS from a TSO session, you must define the TSO user as a console device in the CSD before starting the IVP. For more information, see Defining console devices to CICS.