Perform the following steps:
Before you can run any of the CICS-supplied IVP jobs, create the data sets that they use. For further information about creating the data sets for the IVP jobs, see Creating the CICS data sets.
All the IVP jobs require the CICS Type 3 SVC, which must be installed in the LPA. If you have not already installed the CICS SVC in the LPA (as described under Installing CICS modules in the MVS link pack area), do so now before attempting to run any of the IVP jobs. The IVP jobs do not use the Type 6 SVC (DFHHPSVC).
If you want to use VTAM with a CICS region started by any of the CICS IVP jobs, create and activate a VTAM APPL definition for the CICS regions’s application identifier (applid). The applid defined to VTAM must match the applid that is specified on the APPLID system initialization parameter that is used by the IVP job. For example, to be able to logon to the CICS region that is started by the DFHIVPOL job, you must do one of the following:
For more information about creating and activating VTAM APPL definitions for CICS, see Defining CICS regions as applications to VTAM and Naming conventions.
Further, if you want to use VTAM cross-domain services to communicate between CICS regions on separate MVS images, you must create and activate VTAM CDRSC definitions in both MVS images involved in the communication. For more information about creating and activating VTAM CDRSC definitions for CICS, see Cross-domain considerations.
To run the IVP jobs with external security, you must define to RACF an IVP default CICS userid that has authority to run the transactions used as part of the IVP jobs. These transactions include the CICS-supplied transactions that are listed in Table 16. The level of authority that is required by the IVP userid depends on what security you want to use for the IVP jobs. For more information, see Review security requirements for the IVP jobs.
For information about the security requirements for CICS-supplied transactions, and about CICS security in general, see the CICS® RACF® Security Guide .
Application | Transactions |
---|---|
DFH$BTCH | CWTO, CEMT, CEOT, CSFE |
FILEA samples | |
DFH$MNU | AMNU, MENU, PMNU, DMNU |
DFH$ALL |
AINQ, INQY, PINQ, DINQ AADD, ADDS, PADD, DADD AUPD, UPDT, PUPD, DUPD |
DFH$xBRW | ABRW, BRWS, PBRW, DBRW |
DFH$REN | AORD, OREN, PORD, DORD |
DFH$xCOM | AORQ, OREQ, PORQ, DORQ |
DFH$REP | AREP, REPT, PREP, DREP |
Other functions | CETR, CEDA, CMAC, CMSG, CSGM |
You can run the IVP jobs with or without external security.
As supplied, the system initialization table, DFHSIT, used by the IVP jobs, specifies that external security is on. However, the IVP jobs have been set up with SEC=NO, indicating that external security is not on. DFHSIT also specifies that the IVP jobs are subject to transaction security (XTRAN=YES), resource security (Xyyy=YES), and command security (XCMD=YES).
If you choose to run the IVP jobs with external security, you must:
You must also give the IVP userid sufficient authority to use transactions and resources that are needed to run the IVP jobs. That is, you must:
If you define the transactions as prefixed resources, you must also specify
the system initialization parameter SECPRFX={YES |prefix}
for the IVP
jobs.
For information about implementing external security, see the CICS RACF Security Guide. Alternatively, you can run the IVP jobs with limited security, for example:
CICS automatically attempts to connect to its system log stream, unless you define a journal model resource definition to define the log stream as TYPE(DUMMY). This means that you need to decide whether you want to run the IVPs with system logs, or to run with dummy logging.
If you decide to run with actual log streams, see Defining the logger environment for CICS journaling for information about defining log streams.
Alternatively, you can define a CICS JOURNALMODEL resource definition with TYPE(DUMMY) to avoid having to define log streams. If you want to run the IVPs with the minimum effort:
Note that your group list must follow the IBM-supplied list DFHLIST. DFHLIST includes group DFHLGMOD (which contains DFHLOG and DFHSHUNT JOURNALMODEL definitions) Concatenating your list after DFHLIST ensures that your DUMMY definitions replace the IBM definitions.
//CSDLGSTR JOB 1,BELL,MSGCLASS=A,MSGLEVEL=(1,1),CLASS=A
//CSDUP EXEC PGM=DFHCSDUP,REGION=1M,PARM='CSD(READWRITE)'
//STEPLIB DD DSN=CICSTS31.SDFHLOAD,DISP=SHR
//DFHCSD DD DSN=CICSTS31.CICSH###.DFHCSD,DISP=SHR
//SYSPRINT DD SYSOUT=*
//SYSABOUT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
//SYSUDUMP DD SYSOUT=*
//SYSIN DD *
*
* DEFINE JOURNAL MODELS FOR CICS LOG STREAMS AS DUMMY
*
DEFINE JOURNALMODEL(DFHLOG) GROUP(LOGTEST)
DESCRIPTION(DEFINE SYSTEM LOG AS DUMMY)
JOURNALNAME(DFHLOG)
TYPE(DUMMY)
*
DEFINE JOURNALMODEL(DFHSHUNT) GROUP(LOGTEST)
DESCRIPTION(DEFINE SYSTEM LOG AS DUMMY)
JOURNALNAME(DFHSHUNT)
TYPE(DUMMY)
/*
//
All the IVP jobs use the system initialization parameters that are specified in the associated DFH$SIPn member of the SYSIN data set. The DFH$SIPn members, as supplied by CICS, default to the unsuffixed SIT, DFHSIT, and the resources defined to CICS are adequate only for a basic CICS region. For example, in the case of the DFHIVPOL job, the resources defined limit the number of terminals you can use.
The DFH$SIPn members of the SYSIN data set also contain some system initialization parameters to exclude CICS resources not required by the IVP jobs, or to include some not specified by the default SIT.
One such parameter is TCT=5$, specifying the CICS sample terminal control table, in the hlq.SDFHLOAD library. This TCT defines the pair of sequential input and output devices, CARDIN and PRINTER. (These are the only devices that are defined in DFHTCT5$.)
The DFH$SIPn members of the SYSIN data set may need to be edited for:
The IVP jobs do not require the Type 6 SVC.
Transactions can be defined as prefixed resources
by using the IVP userid, IVPUSER or
any other prefix, as the prefix (for example, IVPUSER.CEMT or prefix.CEMT). To do this, add SECPRFX=YES, or SECPRFX=prefix
in the appropriate DFH$SIPn member for the IVP job.
This enables transactions to be run as part of the IVP jobs without affecting other CICS regions. For example, when the DFH$BTCH batch stream is run, CICS sends authorization requests to RACF for the transactions and identifies them as IVPUSER.xxxx, where xxxx is the transaction ID (CWTO, CEMT, and so on).
The IVP jobs include the required DD statements for the Language Environment libraries as comments.
Other notes about changes to the system initialization parameters for the IVP jobs, and about the IVP jobs generally, are in the sections that describe the IVP jobs.
If you want to use system initialization parameters to modify or enhance the scope of the IVP jobs, see the CICS System Definition Guide for details about the parameters.
[[ Contents Previous Page | Next Page Index ]]