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 up a CICS region and try out the current facilities; for example you can use the master terminal transaction, CEMT, and the resource definition transaction, CEDA. You can also run some CICS sample application programs (for example, the FILEA applications).

You need either an IBM 3270 Information Display System terminal or a console device You can use both if you wish.

If you use an IBM 3270 Information Display System terminal 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 executed from a console device.

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, see Defining an MVS console.

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 a TSO user as a console device.

The DFHIVPOL job invokes the CICS initialization program DFHSIP to start up CICS. The DFHSIP program reads system initialization parameters from the DFH$SIP1 member of the SYSIN data set.

TCT=NO is specified as a SIT override which causes CICS to use the dummy terminal control table, DFHTCTDY. This dummy TCT contains only the CICS and VTAM control blocks that you need for use with VTAM terminals: there are no terminal entries.

For information about system initialization parameters specified as overrides for the run of the DFHIVPOL job, see Specify system initialization parameters for the IVP jobs.

Defining a terminal for the online IVP

You can define a VTAM terminal by either of the following two methods:

  1. Use the autoinstall facility, which is the recommended method, avoiding the need to define terminals to CICS explicitly before they can be used.
  2. Define a terminal explicitly in the CSD, using the DEFINE command of DFHCSDUP, the batch utility for updating the CSD.

Using autoinstall for a VTAM terminal

If you use the autoinstall function of CICS, you avoid the need for each VTAM terminal that requires access to CICS being explicitly defined in the CSD. 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 needed.

When using autoinstall, you should be aware that when CICS processes an autoinstall request, it uses data from the VTAM logmode table. This is an important consideration. An autoinstall request will succeed 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. For programming information about the LOGMODE definitions that match the CICS-supplied model definitions for autoinstall, see the CICS Customization Guide. Before attempting to start CICS and autoinstall a terminal for this IVP, check your VTAM definitions with those given in the CICS Customization Guide. If CICS fails to match model and logmode data, you receive message DFHZC6987I. For information about the suggested course of action if you receive message DFHZC6987I, see the CICS Messages and Codes manual.

CSD resource definitions for autoinstall

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

Group Name
Description
DFHTERM
Model terminal definitions for use with the autoinstall facility. For example, two of the TERMINAL definitions are 3270 and LU2.
DFHTYPE
Partial terminal definitions (TYPETERMs) defining common terminal properties, or attributes. For example, two of the TYPETERM definitions are DFH3270 (to define a non-SNA 3270 terminal) and DFHLU2E2 (to define a SNA 3270 model 2 terminal). The DFHLU2E2 resource definition matches the VTAM-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 in the sample SIT. 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 terminal you will have to do this offline, using the DFHCSDUP utility program. For information about autoinstall definitions, see the CICS® Resource Definition Guide .

Autoinstall also requires a user program to assign terminal 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 terminal 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 terminals, the sample autoinstall user program is called DFHZATDY.)

Defining a VTAM terminal in the CSD

If you want to use an explicitly defined terminal, rather than let CICS autoinstall a terminal, you will need to 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 master terminal, but without a terminal you can only do this using the DFHCSDUP utility program. For an example of a DFHCSDUP job to define a VTAM terminal in the CSD, see Figure 29. For information about the keywords and operands of the DFHCSDUP DEFINE commands, see the CICS Resource Definition Guide .

Figure 29. Defining a terminal 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=CICSTS31.CICS.SDFHLOAD,DISP=SHR
//DFHCSD   DD DSN=CICSTS31.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
/*
//

You must substitute your own values for the operands that are coded in lowercase in the DEFTERM job shown in Figure 29:

TYPETERM
Specify a unique name to identify the resource definition that matches the properties of the type of terminal you are using. For example, to define a SNA 3270 model 2 terminal, specify the CICS-supplied TYPETERM definition DFHLU2E2. For a list of the CICS-supplied TYPETERM definitions, or for information about creating your own definitions, see the CICS Resource Definition Guide .
GROUP
Code a unique name for the group to which the terminal resource definition is to belong.
TERMINAL
Code a unique 4-character terminal identifier as the name by which CICS is to know the terminal.
NETNAME
Code the 8-character VTAM name that identifies this terminal to your VTAM system.
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.

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, make sure you define your new group list to CICS, by adding a SIT override to the SYSIN data set in the DFHIVPOL job stream.

Defining the CICS APPLID to VTAM

You must ensure that either:

If you use the default APPLID (DBDCCICS), define this to VTAM as described in VTAM APPL parameters for CICS regions, before starting the DFHIVPOL job.

Defining an MVS console

If you want to use an MVS console with the DFHIVPOL job, CICS requires an installed definition for the console. You can achieve this using one of the following:

You define these resources using the DFHCSDUP utility program. The CICS-supplied TYPETERM group, DFHTYPE, contains a typeterm definition called DFHCONS, which is predefined with the required console properties. The DFHTERM group, however, does not contain any corresponding terminal entries for MVS consoles. You identify the console by the CONSNAME(name) attribute, even if the TERMINAL definition is an autoinstall model (the console name on an autoinstall model is a dummy value, and replaced by the real console name at install-time).

For an example of the DEFINE command required to define a console, see Figure 30.

For information about defining MVS consoles to CICS, see the CICS System Definition Guide.

Defining a TSO user as a console device

A TSO user can enter MODIFY commands from terminals logged on to TSO, using either the TSO CONSOLE command or from SDSF. MVS activates a console using, by default, the user's TSO user ID as the console name. To CICS, the console name passed on the MODIFY command is treated like an MVS system console, and requires an entry in the CICS system definition (CSD) file.

As in the case of the MVS system console, you can achieve this using one of the following:

You are recommended to define consoles to CICS with preset terminal security, using the USERID attribute on the TERMINAL definition. This avoids the TSO user having to sign on using the CESN transaction. Otherwise, the TSO user's CICS signon password is displayed when entered on the CESN transaction.

For an example of a DEFINE command to define a TSO user, see Figure 30.

Figure 30. Defining a console and a TSO user by using the DFHCSDUP utility program
//DEFTERM  JOB (accounting information),MSGCLASS=A,
//         MSGLEVEL=(1,1),CLASS=A,NOTIFY=userid
//CONSDEF  EXEC PGM=DFHCSDUP
//STEPLIB  DD DSN=CICSTS31.CICS.SDFHLOAD,DISP=SHR
//DFHCSD   DD DSN=CICSTS31.CICS.DFHCSD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSIN    DD *
 
*  Define a console
DEFINE TERMINAL(trmidnt)   GROUP(grpname)     TYPETERM(DFHCONS)
       CONSNAME(consname)   DESCRIPTION(MVS CONSOLE consname)
       USERID(tsouser)
 
*  Define a TSO user as a console device
DEFINE TERMINAL(trmidnt)   GROUP(grpname)     TYPETERM(DFHCONS)
       CONSNAME(tsouser)   DESCRIPTION(TSO USER tsouser)
       USERID(tsouser)
*
 
APPEND LIST(DFHLIST) TO(yourlist)
*
ADD GROUP(grpname) LIST(yourlist)
*
LIST   LIST(yourlist)  OBJECTS
/*
//
Note:
Substitute your own values for the operands that are shown in italics in the DEFTERM job shown in Figure 30.

To include the CICS-supplied list of resources at startup, specify DFHLIST on the GRPLIST system initialization parameter, as well as your own group list name. For example, specify GRPLIST=(DFHLIST,userlista,userlistb)in the CICS SYSIN data set member.

Running the DFHIVPOL job

The DFHIVPOL job includes a procedure, DFHSTART, to start up CICS. When you have successfully logged on to CICS, you can carry out any of the interactive operations described in topic Using CICS-supplied transactions through a terminal.

While logged on to CICS, you should perform a CEMT SET DUMPDS SWITCH to ensure that both dump data sets are initialized before DFHDU640 is run when you shut down CICS.

Finally, you can shut down CICS.

Sample job log for the DFHIVPOL job

When you run the DFHIVPOL job, your job log should look similar to the sample log shown in Figure 31.

Figure 31. Sample job log for the DFHIVPOL job
1 J E S 2  J O B  L O G  --  S Y S T E M  M V 2 6  --  N O D E  W I N M V S 2 C
0
 17.17.29 JOB35727 ---- TUESDAY,   18 JAN 2005 ----
 17.17.29 JOB35727  ICH70001I CICINST  LAST ACCESS AT 16:24:15 ON TUESDAY, JANUARY 18, 2005
 17.17.29 JOB35727  $HASP373 DFHIVPOL STARTED - INIT 69   - CLASS A - SYS MV26
 17.17.29 JOB35727  IEF403I DFHIVPOL - STARTED - TIME=17.17.29
 17.17.29 JOB35727  -                                         --TIMINGS (MINS.)--            ----PAGING COUNTS--- 
 17.17.29 JOB35727  -JOBNAME  STEPNAME PROCSTEP    RC   EXCP    CPU    SRB  CLOCK   SERV  PG   PAGE   SWAP    VIO SWAPS STEPNO
 17.17.29 JOB35727  -DFHIVPOL CICS     CICSCNTL    01     23    .00    .00    .00    167   0      0      0      0     0     1
 17.17.29 JOB35727  -DFHIVPOL CICS     DTCNTL      01     19    .00    .00    .00    147   0      0      0      0     0     2
 17.17.30 JOB35727  DFHPA1101  CICSIVP1 DFHSIT   IS BEING LOADED.
 17.17.30 JOB35727  DFHPA1108  CICSIVP1 DFHSIT   HAS BEEN LOADED. (GENERATED AT: MM/DD= 01/12 HH:MM= 13:57).
 17.17.30 JOB35727  DFHPA1100  CICSIVP1 OVERRIDE PARAMETERS FROM JCL EXEC STATEMENT: START=AUTO,SYSIN
 17.17.30 JOB35727  DFHPA1102  CICSIVP1 OVERRIDE PARAMETERS FROM SYSIN:   1 
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 XRF=NO,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 AUXTR=ON,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 AUXTRSW=NEXT,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 APPLID=CICSIVP1,   2 
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 FCT=NO,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 TCT=NO,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 SRT=NO,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 SEC=NO,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 TRTABSZ=64,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 PGRET=P/,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 PGPURGE=T/,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 PGCOPY=C/,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 PGCHAIN=X/,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 CICSSVC=233,
 17.17.30 JOB35727  DFHPA1927  CICSIVP1 .END
 17.17.30 JOB35727  DFHPA1103  CICSIVP1 END OF FILE ON SYSIN.
 17.17.31 JOB35727  +DFHTR0103 TRACE TABLE SIZE IS 64K
 17.17.31 JOB35727  +DFHSM0122I CICSIVP1 Limit of DSA storage below 16MB is 5,120K.   3 
 17.17.31 JOB35727  +DFHSM0123I CICSIVP1 Limit of DSA storage above 16MB is 30M.
 17.17.31 JOB35727  +DFHSM0113I CICSIVP1 Storage protection is not active.
 17.17.31 JOB35727  +DFHSM0126I CICSIVP1 Transaction isolation is not active.
 17.17.32 JOB35727  +DFHDM0101I CICSIVP1 CICS is initializing.
 17.17.32 JOB35727  +DFHWB0109I CICSIVP1 Web domain initialization has started.
 17.17.32 JOB35727  +DFHSO0100I CICSIVP1 Sockets domain initialization has started.
 17.17.32 JOB35727  +DFHRX0100I CICSIVP1 RX domain initialization has started.
 17.17.32 JOB35727  +DFHRX0101I CICSIVP1 RX domain initialization has ended.
 17.17.33 JOB35727  +DFHLG0101I CICSIVP1 Log manager domain initialization has started.
 17.17.33 JOB35727  +DFHEJ0101 CICSIVP1  296
    296              Enterprise Java domain initialization has started. Java is a
    296              trademark of Sun Microsystems, Inc.
 17.17.33 JOB35727  +DFHDH0100I CICSIVP1 Document domain initialization has started.
 17.17.33 JOB35727  +DFHXS1100I CICSIVP1 Security initialization has started.
 17.17.33 JOB35727  +DFHSI1500 CICSIVP1 CICS startup is in progress for CICS Transaction Server Version 3.1.0
 17.17.33 JOB35727  +DFHDU0304I CICSIVP1 Transaction Dump Data set DFHDMPA opened.
 17.17.33 JOB35727  +DFHXS1102I CICSIVP1 Security is inactive.
 17.17.33 JOB35727  +DFHSI1501I CICSIVP1 Loading CICS nucleus.
 17.17.34 JOB35727  +DFHTR0113 CICSIVP1 Auxiliary trace is being started on data set DFHAUXT.
 17.17.34 JOB35727  +DFHCQ0100I CICSIVP1 Console queue initialization has started.
 17.17.34 JOB35727  +DFHCQ0101I CICSIVP1 Console queue initialization has ended.
 17.17.34 JOB35727  +DFHCQ0103I CICSIVP1 MVS console queue is open.
 17.17.34 JOB35727  +DFHCQ0200I CICSIVP1 CEKL transaction enabled.
 17.17.34 JOB35727  +DFHXS1101I CICSIVP1 Security initialization has ended.
 17.17.34 JOB35727  +DFHRM0141 CICSIVP1 Recovery manager autostart override record is not present. 
																								Normal processing continues.
 17.17.34 JOB35727  +DFHDH0101I CICSIVP1 Document domain initialization has ended.
 17.17.34 JOB35727  +DFHMN0105I CICSIVP1 Using default Monitoring Control Table.
 17.17.34 JOB35727  +DFHMN0110I CICSIVP1 CICS Monitoring is inactive.
 17.17.34 JOB35727  +DFHSO0101I CICSIVP1 Sockets domain initialization has ended.
 17.17.35 JOB35727  IEC031I D37-04,IFG0554P,DFHIVPOL,CICS,DFHAUXT,D306,P2P0C6,INST.CICSTS31.CICS.DFHAUXT
 17.17.35 JOB35727  +DFHTR0110 - AUXILIARY TRACE DATA SET DFHAUXT  FULL - SWITCHING TO DFHBUXT
 17.17.35 JOB35727  +DFHWB0110I CICSIVP1 Web domain initialization has ended.
 17.17.35 JOB35727  IEC031I D37-04,IFG0554P,DFHIVPOL,CICS,DFHBUXT,D50B,P2P14B,INST.CICSTS31.CICS.DFHBUXT
 17.17.35 JOB35727  +DFHTR0109 - AUXILIARY TRACE DATA SET DFHBUXT  FULL - AUXILIARY TRACE HAS BEEN STOPPED
 17.17.35 JOB35727  +DFHSI1502I CICSIVP1 CICS startup is Warm.
 17.17.35 JOB35727  +DFHTS0100I CICSIVP1 Temporary Storage initialization has started.
 17.17.35 JOB35727  +DFHLG0103I CICSIVP1 System log (DFHLOG) initialization has started.
 17.17.35 JOB35727  +DFHLG0104I CICSIVP1  322
    322              System log (DFHLOG) initialization has ended. Log stream
    322              CICINST.CICSIVP1.DFHLOG is connected to structure LOG_GENERAL_008.
 17.17.35 JOB35727  +DFHLG0103I CICSIVP1 System log (DFHSHUNT) initialization has started.
 17.17.35 JOB35727  +DFHSI1503I CICSIVP1 Terminal data sets are being opened.
 17.17.36 JOB35727  +DFHLG0104I CICSIVP1  327
    327              System log (DFHSHUNT) initialization has ended. Log stream
    327              CICINST.CICSIVP1.DFHSHUNT is connected to structure LOG_GENERAL_008.
 17.17.36 JOB35727  +DFHLG0102I CICSIVP1 Log manager domain initialization has ended.
 17.17.36 JOB35727  +DFHKE0406I CICSIVP1  329
    329              CICS is about to wait for predecessors defined in the MVS automatic
    329              restart management policy for this region.
 17.17.36 JOB35727  +DFHKE0412I CICSIVP1 CICS WAITPRED call to automatic restart manager has completed.
 17.17.36 JOB35727  +DFHCP0101I CICSIVP1 CPI initialization has started.
 17.17.36 JOB35727  +DFHPR0104I CICSIVP1 Partner resource manager initialization has started.
 17.17.36 JOB35727  +DFHAI0101I CICSIVP1 AITM initialization has started.
 17.17.36 JOB35727  +DFHFC0100I CICSIVP1 File Control initialization has started.
 17.17.36 JOB35727  +DFHTD0100I CICSIVP1 Transient Data initialization has started.
 17.17.39 JOB35727  +DFHTS0101I CICSIVP1 Temporary Storage initialization has ended.
 17.17.39 JOB35727  +DFHER5730 CICSIVP1 User recovery beginning
 17.17.39 JOB35727  +DFHLG0745I CICSIVP1 System log full scan has started.
 17.17.39 JOB35727  +DFHLG0748I CICSIVP1 System log selective scan has started.
 17.17.39 JOB35727  +DFHLG0749I CICSIVP1 System log scan has completed.
 17.17.40 JOB35727  +DFHER5731 CICSIVP1 No active user records on the system log
 17.17.40 JOB35727  +DFHER5732 CICSIVP1 User recovery completed
 17.17.40 JOB35727  +DFHTD0101I CICSIVP1 Transient Data initialization has ended.
 17.17.40 JOB35727  +DFHFC0101I CICSIVP1 File Control initialization has ended.
 17.17.40 JOB35727  +DFHTC1575 CICSIVP1 No TCT entry for SAMA
 17.17.40 JOB35727  +DFHCP0102I CICSIVP1 CPI initialization has ended.
 17.17.40 JOB35727  +DFHPR0105I CICSIVP1 Partner resource manager initialization has ended.
 17.17.40 JOB35727  +DFHAI0102I CICSIVP1 AITM initialization has ended.
 17.17.40 JOB35727  +DFHAP1203I CICSIVP1 Language Environment is being initialized.
 17.17.40 JOB35727  +DFHAP1200 CICSIVP1 A CICS request to the Language Environment has failed. Reason code '0011020'.
 17.17.40 JOB35727  +DFHAP1208 CICSIVP1 Language Environment cannot support the Cobol language.    7 
 17.17.40 JOB35727  +DFHAP1209 CICSIVP1 Language Environment cannot support the C/C++ languages.   7 
 17.17.40 JOB35727  +DFHAP1210 CICSIVP1 Language Environment cannot support the PL/I language.     7 
 17.17.40 JOB35727  +DFHAP1211I CICSIVP1 Language Environment initialization completed.
 17.17.40 JOB35727  +DFHWB1007 CICSIVP1 Initializing CICS Web environment.
 17.17.40 JOB35727  +DFHWB1008 CICSIVP1 CICS Web environment initialization is complete.
 17.17.40 JOB35727  +DFHSI1517 CICSIVP1 Control is being given to CICS.
 17.17.40 JOB35727  +DFHEJ0102 CICSIVP1 Enterprise Java domain initialization has ended.
 17.23.42 JOB35727  +DFHFC0208I CICSIVP1  069
    069              LSR pool 1 is being built dynamically by CICS because all of the
    069              necessary parameters have not been supplied. Either there is no
    069              LSRPOOL definition or it is incomplete. The following are not
    069              defined:  'CI SIZE' 'STRINGS' 'MAXKEYLENGTH'. A delay is possible.
 17.24.17 JOB35727  +DFHFC0208I CICSIVP1  137
    137              LSR pool 1 is being built dynamically by CICS because all of the
    137              necessary parameters have not been supplied. Either there is no
    137              LSRPOOL definition or it is incomplete. The following are not
    137              defined:  'CI SIZE' 'STRINGS' 'MAXKEYLENGTH'. A delay is possible.
 17.24.28 JOB35727  +DFHTM1715 CICSIVP1 CICS is being quiesced by userid CICSUSER in transaction CEMT 
																									at netname IYCQTC70.   4 
 17.24.28 JOB35727  +DFHDM0102I CICSIVP1 CICS is quiescing.
 17.24.28 JOB35727  +DFHTM1782I CICSIVP1 All non-system tasks have been successfully terminated.
 17.24.28 JOB35727  +DFHZC2305I CICSIVP1 Termination of VTAM sessions beginning
 17.24.28 JOB35727  +DFHCESD  CICSIVP1 SHUTDOWN ASSIST TRANSACTION CESD STARTING. SHUTDOWN IS NORMAL.
 17.24.29 JOB35727  +DFHZC2316 CICSIVP1 VTAM ACB is closed
 17.24.29 JOB35727  +DFHCQ0104I CICSIVP1 MVS console queue is closed.
 17.24.31 JOB35727  +DFHRM0204 CICSIVP1 There are no indoubt, commit-failed or backout-failed UOWs.
 17.24.32 JOB35727  +DFHRM0130 CICSIVP1 Recovery manager has successfully quiesced.
 17.24.32 JOB35727  +DFHDU0303I CICSIVP1 Transaction Dump Data set DFHDMPA closed.
 17.24.32 JOB35727  +DFHKE1799 CICSIVP1 TERMINATION OF CICS IS COMPLETE.
 17.24.33 JOB35727  -DFHIVPOL CICS     CICS        00   5757    .02    .00   7.05  21599   0      0      0      0     0     3
 17.24.33 JOB35727  -DFHIVPOL CICS     PRTDMPA     00    136    .00    .00    .00    286   0      0      0      0     0     4
 17.24.34 JOB35727  -DFHIVPOL CICS     PRTDMPB     00    135    .00    .00    .00    285   0      0      0      0     0     5
 17.24.37 JOB35727  -DFHIVPOL CICS     PRTAUXT     00   1559    .01    .00    .05  13828   0      0      0      0     0     6
 17.24.37 JOB35727  $HASP375 DFHIVPOL ESTIMATED  LINES EXCEEDED
 17.24.38 JOB35727  $HASP375 DFHIVPOL ESTIMATE EXCEEDED BY               5,000  LINES
 17.24.38 JOB35727  $HASP375 DFHIVPOL ESTIMATE EXCEEDED BY              10,000  LINES
 17.24.38 JOB35727  $HASP375 DFHIVPOL ESTIMATE EXCEEDED BY              15,000  LINES
 17.24.38 JOB35727  $HASP375 DFHIVPOL ESTIMATE EXCEEDED BY              20,000  LINES
 17.24.39 JOB35727  $HASP375 DFHIVPOL ESTIMATE EXCEEDED BY              25,000  LINES
 17.24.39 JOB35727  $HASP375 DFHIVPOL ESTIMATE EXCEEDED BY              30,000  LINES
 17.24.39 JOB35727  $HASP375 DFHIVPOL ESTIMATE EXCEEDED BY              35,000  LINES
 17.24.40 JOB35727  -DFHIVPOL CICS     PRTBUXT     00   1572    .01    .00    .05  13923   0      0      0      0     0     7
 17.24.40 JOB35727  IEF404I DFHIVPOL - ENDED - TIME=17.24.40
 17.24.40 JOB35727  -DFHIVPOL ENDED.  NAME-CICINST              TOTAL CPU TIME=   .06  TOTAL ELAPSED TIME=  7.18
 17.24.40 JOB35727  $HASP395 DFHIVPOL ENDED

Notes:

 1  For information about the system initialization parameters used by the IVP jobs, see topic Specify system initialization parameters for the IVP jobs. (See also  2  and  3  below.)

 2  For more information about defining an applid for the CICS IVP jobs, see Defining CICS regions as applications to VTAM. An applid of CICSIVP1 has been used in Figure 31 page=no.

 3  The DFHSM0122 messages inform you of the limits available for the dynamic storage areas below and above 16MB. For information about these storage areas, see the CICS System Definition Guide .

Note:
Storage for the extended read-only DSA, ERDSA, is obtained from read-only key 0 protected storage, because the sample SIT specifies RENTPGM=PROTECT (the default).

 4  The DFHTM1715 message is issued because the CICS region was shut down by the terminal user (with netname IYCWTC30) issuing a CEMT PERFORM SHUTDOWN command.

 7  If you want COBOL, C, C++ and PL/I languages, remove the comment marks from the SCEERUN and SCEERUN2 libraries, and increase the memory size for the job.

Logging on at a VTAM terminal

When the DFHIVPOL job displays the console message CONTROL IS BEING GIVEN TO CICS, you can log on to CICS using an IBM 3270 Information Display system terminal. Use the CICS application identifier that you specified when you brought up CICS to log on through your VTAM terminal. For example, unless you changed the APPLID specified as a SIT override parameter, (it is CICSIVP1), enter LOGON APPLID(CICSIVP1).

If you are using autoinstall, your logon request is passed to CICS and, provided all the autoinstall requirements described in Using autoinstall for a VTAM terminal have been met, CICS installs your terminal. It does this by creating a TCT terminal entry (TCTTE) using the model definitions defined in the group list, DFHLIST, and the terminal identifier returned by the autoinstall user program (DFHZATDX in this case).

If you are using a terminal defined in the CSD explicitly, and included in the group list specified in the startup job stream, CICS identifies the installed resource definitions by the VTAM net name, and creates the required TCTTE.

When you log onto CICS, your terminal can display a "good morning" message, by the transaction specified on the GMTRAN system initialization parameter. The default transaction, CSGM, displays the message shown in Figure 32, as defined by the GMTEXT system initialization parameter.

Note:
For Accessibility: If your browser does not show the following figure in a way that is readable for you, please be aware that the figure includes the word CICS in large letters which are composed of the symbols * and / with the registered trademark symbol shown as (R)
Figure 32. Screen layout for default logon message transaction, CSGM
               WELCOME TO CICS      12:56:28
 
 
 
 
 
                    ******\  ******\  ******\   ******\(R)
                   ********\ ******\ ********\ ********\
                   **\\\\**\   **\\\ **\\\\**\ **\\\\**\
                   **\    \\   **\   **\    \\ **\    \\
                   **\         **\   **\       *******\
                   **\         **\   **\        *******\
                   **\         **\   **\         \\\\**\
                   **\   **\   **\   **\   **\ **\   **\
                   ********\ ******\ ********\ ********\
                    ******\\ ******\  ******\\  ******\\
                     \\\\\\   \\\\\\   \\\\\\    \\\\\\ 
 
 

Using CICS-supplied transactions through a terminal

After you have started CICS with the DFHIVPOL job, you can use the CICS-supplied transactions to try out various functions of CICS, to help you verify that CICS is working properly. You can use the transactions at a CICS terminal and, if you defined one, the system console.

Table 18 shows some typical terminal interactions, including use of the CEMT transaction. For information about the CICS transactions that you can try with the DFHIVPOL job, and about the message-switching responses to those transactions, see the CICS Supplied Transactions manual.

Table 18. Typical terminal interactions
Operator Input System Response
CEMT Status: ENTER ONE OF THE FOLLOWING
    Discard
    Inquire
    Perform
    Set
I
Status:  ENTER ONE OF THE FOLLOWING
OR HIT ENTER FOR DEFAULT
(Followed by a list of options)
PROG
Press ENTER key
STATUS:  RESULTS - OVERTYPE TO MODIFY
Prog(CEECBLDY) Len(0000000) Ass Pro Ena Pri
      Res(000) Use(0000000000) Any Cex Ful
Press PF3 key
Press CLEAR key
CEMT PERFORM STATISTICS
Press PF3 key
Press CLEAR key
SESSION ENDED
CETR
See
Screen layout for the CETR transaction
 
Press PF3 key
Press CLEAR key
Clear or PF3 pressed
Normal termination of CETR
CEMT I TA Displays list of tasks in the system
Press PF3 key
Press CLEAR key
SESSION ENDED
CEMT I
PROG(DFHFEP)
Prog(DFHFEP )Len(005848) Ass Pro Ena Pri
       Res(000) Use(0000000) Any Cex Ful Qua

Press PF3 key
Press CLEAR key
SESSION ENDED
CEOT
(Inquire about this
terminal)
Ter (tmid) Tra (CEOT) Pri (nnn) Pag Ins Ati Tti
(Remember 'tmid' for use in next transaction, CMSG)
Press PF3 key
Press CLEAR key
SESSION ENDED
 
CMSG 'HELLO',R=tmid,S
(Send the message 'HELLO' to your terminal)
MRS OK MESSAGE HAS BEEN ROUTED
(briefly at bottom right of screen)
HELLO
(at top left of screen)

You may enter your CEMT input in either uppercase or lowercase, because the master terminal transaction translates all input to uppercase. Use the CLEAR key and the PF3 key as indicated.

If you enter the CETR transaction, CICS displays the status of the various trace options. The screen layout in Figure 33 shows what the CETR display looks like. For information about the CETR transaction, and the other information panels available by using specified PF keys, see the CICS Supplied Transactions manual.

Figure 33. Screen layout for the CETR transaction
CETR                    CICS/ESA Trace Control Facility       sysid applid
 
Type in your choices.
 
Item                              Choice       Possible choices
 
Internal Trace Status       ===>  STARTED      STArted, STOpped
Internal Trace Table Size   ===>  64      K    16K - 1048576K
 
Auxiliary Trace Status      ===>  STOPPED      STArted, STOpped, Paused
Auxiliary Trace Dataset     ===>  B            A, B
Auxiliary Switch Status     ===>  NO           NO, NExt, All
 
GTF Trace Status            ===>  STOPPED      STArted, STOpped
 
Master System Trace Flag    ===>  ON           ON, OFf
Master User Trace Flag      ===>  ON           ON, OFf
 
When finished, press ENTER.
 
 
 
 
PF1=Help      3=Quit      4=Components      5=Ter/Trn     9=Error List

You can alter the status of any of the trace options by overtyping the current value, indicated by ===> on the CETR display.

Using the CEDA transaction

When DFHIVPOL starts up CICS, it uses the unsuffixed SIT, DFHSIT. This system initialization table specifies GRPLIST=DFHLIST, causing all the CICS resource definitions that are needed for normal running to be installed. You can see which resources are included in DFHLIST by using the CEDA transaction. For example,
CEDA EXPAND LIST(DFHLIST) gives a screen similar tosimilar to that in Figure 34.

Press PF8 to see the continuation of the list. If you started the DFHIVPOL job with your own group list specified instead of the DFHLIST group list, specify the name of your list in the CEDA EXPAND command. The CICS-defined groups all begin with DFH. For information about CEDA and the interactions for a typical sequence of CEDA commands, see the CICS Resource Definition Guide.

Figure 34. Screen layout for CEDA EXPAND LIST(DFHLIST) command
 
 EXPAND LIST(DFHLIST)
 ENTER COMMANDS
  NAME     TYPE         LIST                                    DATE   TIME
  DFHDCTG  GROUP        DFHLIST                                 95.349 15.49.57
  DFHBMS   GROUP        DFHLIST                                 95.349 15.49.57
  DFHCONS  GROUP        DFHLIST                                 95.349 15.49.57
  DFHDBCTL GROUP        DFHLIST                                 95.349 15.49.57
  DFHDB2   GROUP        DFHLIST                                 95.349 15.49.57
  DFHEDF   GROUP        DFHLIST                                 95.349 15.49.57
  DFHEDP   GROUP        DFHLIST                                 95.349 15.49.57
  DFHFE    GROUP        DFHLIST                                 95.349 15.49.58
  DFHHARDC GROUP        DFHLIST                                 95.349 15.49.58
  DFHINQUI GROUP        DFHLIST                                 95.349 15.49.58
  DFHINTER GROUP        DFHLIST                                 95.349 15.49.58
  DFHISC   GROUP        DFHLIST                                 95.349 15.49.58
  DFHMISC  GROUP        DFHLIST                                 95.349 15.49.58
  DFHMSWIT GROUP        DFHLIST                                 95.349 15.49.58
  DFHOPCLS GROUP        DFHLIST                                 95.349 15.49.58
  DFHOPER  GROUP        DFHLIST                                 95.349 15.49.58
+ DFHPGAIP GROUP        DFHLIST                                 95.349 15.49.58
 
                                                     SYSID=CICS APPLID=CICSIVP1
  RESULTS: 1 TO 17 OF 47                       TIME:  16.09.50  DATE: 95.349
PF 1 HELP       3 END 4 TOP 5 BOT 6 CRSR 7 SBH 8 SFH 9 MSG 10 SB 11 SF 12 CNCL

The DFHLIST group list does not include any of the sample applications groups, the group names of which all begin with DFH$. To use the sample programs, therefore, you must first install the resource definitions for the required samples. For example, to use the FILEA sample application:

  1. Install the sample programs that are needed for the FILEA applications. You can do this by the command:
    CEDA INSTALL GROUP(DFH$AFLA)
  2. Make the FILEA data set available to CICS. You can do this by one of the following:

To end the CEDA session, press PF3.

Invoking and executing sample programs

To try the assembler-language version of the FILEA sample application, install group DFH$AFLA then enter the AMNU transaction.

For information about the CICS sample application programs, see CICS 4.1 Sample Applications Guide .

Using transactions from a console device

CICS transactions (other than CECI) can be invoked from a console device, and other CICS operators can communicate with the console operator. In particular, you can use the console device for CICS master terminal functions, to control CICS terminals or to control several CICS regions in conjunction with multiregion operation. Normal operating-system use of the console device is not inhibited, and CICS supports multiple console devices where present.

Notes:
  1. The CEDA transaction can be used from a console device only to INSTALL resource definitions.
  2. The CECI transaction and the sample programs cannot be used from a console device.

If you issue the MVS command d consoles, this displays a list of console devices. This list identifies the console devices by name.

You can use a console device to submit MODIFY commands from your job stream if you define a console device in your CSD as CONSNAME(INTERNAL).

For further information about defining consoles, see Defining an MVS console. For further information about defining TSO users as consoles, see Defining a TSO user as a console device.

To enter a command, use:

{MODIFY|F}  jobname,[']command[']

where:

jobname
is the region identifier for the CICS region. This is either the name of the job being used to execute CICS (for example, DFHIVPOL) or the name of a procedure if CICS was initiated as a started task.
command
is a string of data, starting with a CICS transaction identifier. If the transaction requires further input, the operator is prompted in the same way as any normal terminal operator. The message from CICS contains a reply number that must be quoted in the reply.

You can use the commands shown in Figure 35 to verify the CEMT and CEOT transactions from the MVS console. (For information about these transactions, see the CICS Supplied Transactions manual.)

Entering commands from TSO

A TSO user can enter CICS commands as above after invoking the TSO command CONSOLE, in either of the following formats:

    CONSOLE {MODIFY|F}  cicsid,[']command[']
 
    CONSOLE
    {MODIFY|F}  cicsid,[']command[']
    END

When the TSO command CONSOLE is used, TSO checks the user for authority to issue console commands. Further, if console operator command security is active, the TSO user must be specifically authorized to issue MODIFY cicsid.

The TSO user can interact with an alternate CICS by using the command CONSOLE MODIFY altcics,CEBT.

You can also use TSO CLIST processing to issue sequences of CICS commands.

Figure 35. Using an MVS console for master terminal operations
Operator Input                   System Response
 
f dfhivpol,'cemt i terminal'     Displays a list of terminals attached
                                 to CICS
 
f dfhivpol,'cemt i dump'         Displays status of transaction dump
                                 data sets
 
f dfhivpol,'cemt p statistics'   CICS writes statistics to SMF data sets
 
f dfhivpol,'cemt i ta'           Displays number and types of tasks
                                 currently running
 
f dfhivpol,'cemt p dump'         CICS invokes SDUMP macro for system
                                 dump to be taken
 
f dfhivpol,'cemt i prog(dfhpep)' Displays details of DFHPEP module
 
f dfhivpol,'ceot'                Displays details of operator console
 
f dfhivpol,'cemt i journalname'  Displays status of CICS logs

Terminating CICS

To terminate CICS, enter: CEMT P SHUT from the VTAM terminal or MVS console. (This is a short form of CEMT PERFORM SHUTDOWN.) The system responds with message DFH1713, and those that follow, as shown in the sample job log shown in topic Figure 31.

[[ Contents Previous Page | Next Page Index ]]