Step 15. Bring up IMS and Check It out

The following example members are provided in the hlq.JCL library, to help you setup the online IMS system:

• COPECTL Control region
• COPEDLS DLS region
• COPEDBRC DBRC region
• COPEMSG1 Message region
• COPEMSG2 Message region
• DF SVSM00 VSAM/OSAM buffer pools member

The following considerations should be reviewed:

1. COPE needs to run LSO=S. This control region parameter causes the DLS (DLI Separate address space) region to run. COPE needs LSO=S so that the PSB and DBD pools can be large, without impacting CSA. You must specify the PSB pool and DMB pool to be your current size times the number of Lsys's. Typical values are 1.5M each, for large systems. As with a non-COPE system, you want your DMB pool to be large enough to hold all of your DBDs, and your PSB pool to hold at least one PSB per message region. COPE PSBs are large. This PSB pool size refers to the DLIPSB JCL parameter. The CSAPSB parameter should be about 10% (one tenth) of DLIPSB.
2. COPE needs "online change" ACBLIBA/B, MODBLKSA/B. MATRIXA/B. This is so that you can easily do ACBGENs, and MODBLKS IMSGENs. The ACBLIBs you specify in the control region JCL must match exactly those you specify in the DLS region JCL.
3. All libraries on the control region STEPLIB, DFSESL, MODBLKSA/B and MATRIXA/B DDs must be authorized.
4. A COPEPGM DD must be added to the Control Region which points to the unauthorized XCOPEPGM (STUBX library). This is used to read in translation X-ref tables, for /FOR commands and messages to MTO. It must be unauthorized. This is not a security exposure, be cause no executable code is loaded from this DD. It is just like the unauthorized ACBLIB and FORMAT libraries that you already have in your Control Region JCL.
5. The COPE message regions execute a special authorized program, COPERC00, instead of DFSRRC00. This is so that COPE can use PC/AUTH to switch the Tasklib, and to vary the DB2 plan names. The message region STEPLIB has to be an authorized library containing COPERC00 (the dynamic allocation load library, DYNLOAD, is recommended). You put libraries you would usually put on your message region STEPLIB (including RESLIB) onto a special COPESTEP DD.
6. The COPESTEP DD is not authorized. You put the XCOPEPGM library (which contains COPE's STUBXs) and the XCOPE1.LOAD library (the COPE software) on top of the COPESTEP. Next, you put libraries that are common to all Lsys's on the COPESTEP (for example, the COBOL run library, RESLIB, etc.). If you are importing programs into COPE, they will go into the XCOPEPGM library, with C-number names. If you are not importing programs, the libraries for each Lsys are not specified in the JCL; instead COPE will dynamically allocate them. This is so that they can be de-allocated without stopping and starting message regions. These Lsys libraries (which are defined in option 1.5) will be "concatenated" ahead of the COPESTEP libraries, so you can put common libraries on the COPESTEP, and leave these common libraries out of the option 1.5 specifications.
7. The option 1.5 Tasklib libraries, and the COPESTEP libraries together behave exactly like a STEPLIB in a non-COPE system. The reason for this is in the architecture of MVS; a STEPLIB is in fact a Tasklib (of the topside task). COPE uses the MVS Tasklib feature in the same way as other systems, for example, ISPF and its ISPLLIB.
8. The message region DFSESL has to be authorized.
9. Check that you use the same RESLIB in all regions' JCL. Mismatched IMS system modules in different RESLIBs will cause IMS waits or loops. You must provide buffers for your databases in the Control Region //PROCLIB DFSVSMnn member. In particular, if you use OSAM USTDLMGR, with block size 22528 (as we recommend), check that you have
   IOBF=(22K,16,N,Y)
   If you don't do this, IMS will give you a DFS0730I message with code A,10, but no further explanation of what is wrong. You must COLD start, after fixing DFSVSMnn (AUTO=N, /NRE CHKPT 0).
10. You must either specify 005 (class 5) as one of the classes on your message region parameter, or have changed the delivered COPE system transaction class, in option 1.7. To do this, go into option 1.7, change the (TP,1) parameters that you will see there, then run option 4.1, then submit IMSGJCL.
11. Add a COPEMENU DD to the message region JCL pointing to your XCOPE1.MENUS library (note the S on the end). COPE will simulate ISPF panel processing for its main screen (member COPEO) and its help screens (COPETOxx). You can customize what appears on these screens in much the same way as you would customize ISPF panels (described in "Customizing the COPE screen"). It is especially useful to set up PF Keys that are meaningful for users at your installation, and this is very easy to do.
12. Add COPEJCL DD pointing to XCOPE1.JCL. This is used for submitting JCL, for SUB, BACKUP and RESTORE commands.
13. If you get "COPEMFSX missing" messages, perform option 4,7 (4.MFS).
14.  If you run Fast Path Expedited Message Handling (IFP regions) you must convert the JCL for those regions by importing it into a Libset using option T, and then regenerating it. For instructions on how to do this, see "Convert external names to COPE internal names (Option T)” in the BMC-COPE-Administration-Guide. This conversion is required because COPE changes the PSB name to an internal C-number.

The SSM member should be defined and appropriate PROCLIB definitions made.

Make sure that the supplied PSBs, DBD and MFS formats are generated, as described in the COPE for IMS/DC Installation Guide. Entering COPE from a cleared screen after you are connected to the physical IMS system will bring up the main COPE screen, which lists the Lsys's that are available. You then "Connect", or "Logon", to an Lsys by typing in its name. After clearing the screen, from this point on, operation is the same as in a non-COPE system.

You should view the online tutorial (by pressing <PF1> from the COPE screen) and then press <Enter>, the same way as in an ISPF tutorial. You can exercise Start/Stop Database/Transaction, which is accessed by typing SS from the COPE screen. These facilities are described in the COPE for IMS DC Programmer’s Guide.

User applications are at this point. The Lsys identifying tokens are in the JCL and Batch jobs executed.