CAIENF Best Practices › Installation Considerations › Upgrades

Previous Topic: Files

Next Topic: Multiple Systems

Upgrades

A big change that started with CAIENF r12 is that the CAS9DB utility is no longer used. For releases of CAIENF prior to r12, the CAIENF database was mandatory and CAS9DB was the utility used to initialize and populate the database with DCM definitions. With CAIENF r12 and above, the database is now optional and only required if event recording is desired. For more information, see CAIENF Installation Considerations in this guide.

If event recording is turned on, the database is only used for event data. The database is no longer used to house DCM information. Rather, CAIENF now directly loads and reads DCM modules as part of CAIENF startup. CAIENF Parameters now tell CAIENF which DCMs to try to load and interrogate. A new CAIDCM DD statement points at the data sets that hold the product DCMs.

The following table provides the CA Common Services r12 and above equivalent of old CAS9DB functions:

CAS9DB DBIN Statement

CAIENF r12 and Above Equivalent

INST DB(ENFDB) DCM(xxxxxxxx)

CAIENF Parameter control statement:

DCM(xxxxxxxx)

and in CAIENF Procedure:

//CAIDCM DD DSN=hlq.CAIDCM,…

// DD DSN=hlq.product.llq

ALTER DB(ENFDB)

EVENT(xxxxxxxx) OPT(A,R,P)

RETPD(nn)

CAIENF Parameter control statements:

EVENT(xxxxxxxx,ACT)

EVENT(xxxxxxxx,REC)

EVENT(xxxxxxxx,RP=n)

EVENT(xxxxxxxx,PURGE=Y)

LIST DB(*) DETAIL

Use the new CAS9DCMR utility for DCM event information.

Use the CASQL003 sample job in the CAW0JCL data set to obtain recorded event record counts.

QUERY DB(*) SELECT ……

CA Datacom/AD DBSQLPR utility.

See CASQL001, 002, 003 CAW0JCL data set sample members.

INST DB(ENFDB) DCM(xxxxxxxx)

REPLACE

Use CAS9DCMR utility SYSPUNCH output data set DROP TABLE statements as input to CAW0JCL member CASQL004. Run CAW0JCL member CADB001 and CASQL004 with CAIENF down, but with an external MUF active.

Some products require an updated level of their DCM to be compatible with CAIENF r12 and above. The CA Common Services for z/OS cover letter supplies CA product PTF numbers or higher product release numbers that must be in place to run with CAIENF r12 and above. If these PTFs have not been applied yet, they can be applied before upgrading to CAIENF Version 14.0.

If you don’t have your previous release CAIENF CAS9DB database initialization jobs handy, a utility is available to interrogate the output of a CAS9DB LIST DB(*) DETAIL report and create the appropriate CAIENF ENFPARM statements. The CAS9DB report must be run while you are still running the previous release of CAIENF.

Use the following JCL to obtain a CA Common Services r11 detail listing:

//CAS9DB   EXEC PGM=CAS9DB,REGION=4096K,TIME=1440
//STEPLIB  DD DSN=YOUR.COMMON.SERVICES.R11.CAILIB,DISP=SHR   => Update
//DBOUT    DD DISP=(NEW,CATLG),                                    
//         DSN=YOUR.R11.ENFDB.LISTING,                 => UPDATE
//         UNIT=3390,VOL=SER=??????,SPACE=(CYL,(1,1)),             
//         DCB=(RECFM=FBA,LRECL=133,BLKSIZE=6118)                  
//DBIN     DD *
  LIST DB(*) DETAIL
/*

Once you have obtained a detail listing, see the CA Common Services SAMPJCL member ENFUTIL for instructions on how to edit the ENFUTIL JCL. The output from the ENFUTIL job can be placed within the member or data set referenced by the ENFPARMS DD in your CAIENF startup procedure.