In this section: How to: |
Prior to using the server and configuring the Adapter for Millennium using the Web Console, you need to edit the server IRUNJCL procedure.
Procedure overview:
Your system support staff can supply proper data set names for your site. The Millennium API modules must be MVS-loadable.
The server must allocate the specific files of the adapter in the IRUNJCL, as well as in a global profile (EDASPROF.CFG).
Edit the IRUNJCL and EDASPROF.CFG as follows:
IRUNJCL. Millennium load library and Control files and databases:
//M30000 DD DISP=SHR,DSN=millen.ctrlfile.M30000 //M30002 DD DISP=SHR,DSN=millen.ctrlfile.M30002 //database DD DISP=SHR,DSN=millen.database
The IRUNJCL must have the following data sets allocated to the following DDNAMEs.
EDASPROF.CFG. Millennium Access File data set allocation
//* Millennium ALLOCATIONS
DYNAM ALLOC F FOCPRV DA qualif.FOCPRV.DATA SHR REUSE
where:
Is the high-level qualifier for your Millennium production data sets.
Is the Millennium control file.
Is the DDNAME required by Millennium for a Millennium database. If you access more than one Millennium database, you must allocate more than one DDNAME, each determined by the options chosen when your site installed Millennium.
Is the high-level qualifier for your server production data sets.
To activate the Adapter for Millennium Tracing Facility, you must allocate DDNAME GPTRACE in the server JCL:
//GPTRACE DD SYSOUT=*
Note: Use the adapter Tracing Facility carefully. The DDNAME is allocated to the server JCL; therefore, it is applied globally. This causes the adapter activity to be traced for all server tasks. This facility should be used under tightly controlled testing circumstances.
iWay Software |