Configuring Your Product › Customization Options › The CA Disk SVC › Installing the CA Disk SVC

Installing the CA Disk SVC

To install the CA Disk SVC, perform the following procedure:

1. Based on the previous discussion; determine which SVC mode of operation you want to use. If you select mode 4, the default mode, skip the remainder of this substep and proceed to substep 2. If you select mode 5 or mode 6, you must change the supplied source code for the variable SVCMODE from C'4' to C'5' or C'6', corresponding to the mode you selected.
2. Decide whether the CA Disk SVC maintains the job name or the accounting code. Then, update the source code in member ADSOPJBM provided in CCUWSAMP library to reflect your selection. The default is to keep the creating JOBNAME. If this is appropriate, skip to substep 3.

   The macro, $JOBNM, has two parameters: FLD and TYPE. The parameter FLD defines the field to maintain. Valid values are ACCT or JOB. To maintain a job name, specify this parameter with a value of JOB. The parameter TYPE defines when this field is updated based on SVCMODE. Valid values are CREATE, MOD, or USE. To have the field updated each time the data set is accessed, set this parameter to a value of USE and set SVCMODE toThe following is an example of the use of this macro:

   $JOBNM FLD=ACCT,TYPE=CREATE 
   

   With the macro coded in this way, the CA Disk SVC maintains the first eight bytes of the creating job's accounting for each data set.

   See Installation library member USERMODN to assemble and link ADSOPJBN into the CA Disk SVC.

3. Determine which SVC number to use for the CA Disk SVC. The CA Disk SVC is normally installed as number 244. 244 is used by some IBM system products as well as other packages. If SVC 244 is already assigned in your system, select a different number for the CA Disk SVC.

   If CA Disk can use SVC 244, proceed to step 4.

   Ensure that the SVC is in the IEASVCxx member of your system parmlib. It should be a type 3 or type 4 SVC, enabled for interrupts. Designating as either restricted or non-restricted is optional.

4. Determine whether any of the fields maintained by the CA Disk SVC will cause a problem at your site. Problems can occur if there are other products that maintain fields in the F1-DSCB. Problems can also occur if packed format is used for Last Modified and Last Use dates, because 4 bytes will be needed to store each one of these dates overlaying other fields in the Format 1 DSCB unless the involved field offsets are adjusted accordingly. If any of the other fields causes a problem, modify the CA Disk SVC to either move the field or not maintain the field.

   To move a field, take the equate label from the following table and modify the SVC source to equate the label to the new value (minus 44) and set the corresponding CA Disk sysparm from the following table to the same value (not minus 44).

   To not maintain a field, take the equate label from the following list and modify the SVC source to comment out any code that uses the equate to examine or change the DSCB, then set the corresponding CA Disk sysparm from the following list to a value of 000 in your parmlib data set:

   SVC Equate Label: DMSUSEDT

   Last opened date (SU 60).

   Sysparm Name: DSCBLUSD

   Default Value: 75

   SVC Equate Label: DMSDSIND

   Change bit x’02’ (SU 60).

   Sysparm Name: n/a

   Default Value: 93

   SVC Equate Label: DMSMODDT

   Last modified date.

   Sysparm Name: DSCBLMOD

   Default Value: 70

   SVC Equate Label: DMSSVCMO

   CA Disk SVC mode.

   Sysparm Name: DSCBSVMD

   Default Value: 103

   SVC Equate Label: DMSJOBNM

   Job name or accounting code.

   Sysparm Name: DSCBJBNM

   Default Value: 62

   SVC Equate Label: DMSOPCNT

   Open count (two bytes).

   Sysparm Name: DSCBOPCD

   Default Value: 73

   The value of each SVC equate label (minus 44) must be equal to the value of the corresponding CA Disk sysparm.

5. A diagnostic facility exists within the SVC that can display applicable data used to determine if DSCB updates are to be made to maintain fields within the DSCB. These diagnostic messages are automatically generated if the job name is equal to the job name identified in field DIAGNAME. The default name is DMSTEST. To change the job name used to generate diagnostic messages, update the DIAGNAME field.

   Note: A change to the DIAGNAME (DMSTEST) will require re-assembling the ADSMVS60 module, (USERMOD1) after updating the source provided in the CCUWSAMP library.

   Similar diagnostic facilities are provided for the VSAM date stamp module and auto-restore catalog management hook. If you change the job name for the SVC, consider changing the job names used for the other diagnostic facilities. This is discussed where applicable for the other functions later in this section.

6. If you have installed a version of the CA Disk SVC from a release prior to Release 8.1, you can have compatibility problems when using CA Disk SVC. See the CA Disk SVC section for a discussion of these problems and how to correct them.
7. The CA Disk SVC is now installed into the CA Disk LPA List library. It does not need to be copied to SYS1.LPALIB. You only need to add the CA Disk LPA List library to your Systems LPA list.

   A copy of the CA Disk SVC with default values is placed in the CA Disk LPA List library at product installation time. If the default values are appropriate for your installation, you do not need to reassemble the SVC.

   To change any of the default values, make your changes to the source found in member ADSMVS60 of the CCUWSAMP. Then run job USERMOD1 in the installation library to reassemble and link the SVC into the CA Disk LPA List library.

   If you are running MVS 2.2.0 or higher, you do not have to change the name of the CA Disk SVC to IGC00nnn in order to install it. However, install the SVC by adding the following line to the IEASVCXX member of your SYS1.PARMLIB:

   SVCPARM 244,REPLACE,TYPE(4),APF(NO),EPNAME(ADSMVS60)
   

8. To activate the SVC, it must be called as part of the processing for each disk data set. Applying a zap to the proper IBM module for your operating system does this. The following list contains the IBM module names to be zapped depending on IBM product level. Apply 1 or more of the following:

   IBM Module: IFG0194A

   CSECT: IFG0194E

   DFP/DFSMS Level: All levels

   MODEL: ZUZMODEL

   USERMOD: USERMOD2

   IBM Module: IGC0001I

   CSECT: IFG0196W

   DFP/DFSMS Level: All except DFP 2.4 and below

   MODEL: ZOZMODEL

   USERMOD: USERMODH

   IBM Module: IGGDADSM

   CSECT: IGGDAU01

   DFP/DFSMS Levels:

   • DFSMS 1.2 w/UW28103
   • DFSMS 1.3 w/UW28104
   • DFSMS 1.4 and above

   MODEL: ZZZMODEL

   USERMOD: USERMODI

   IBM Module: IGC00020

   CSECT: IFG0201R

   Levels:

   • DFSMS 1.2 w/UW28103
   • DFSMS 1.3 w/UW28104
   • DFSMS 1.4 and above

   MODEL: ZYZMODEL

   USERMOD: USERMODJ

   There are many levels of the IBM modules, and each requires a slightly different form of the zap. Zaps to match these maintenance levels are provided in the installation library. Use the one in which all the VERs match your version of the IBM modules. To accomplish this, locate your Operating System level in the preceding table and do the following:

   • Get a zap dump of the IBM module
   • Use SMP to determine the RMID of this same module

     Note: Try to match the RMID to a corresponding member in the CA Disk installation library named ZUAnnnnn or Z1nnnnn. If you cannot find a supplied zap that matches your Operating System level, use a model zap and adjust it to fit. In the MODEL column of the preceding Table, corresponding to your system level, is the name of a member in the installation library. If you need assistance in making the adjustments, contact the CA Disk Technical Support Center.

   • Make sure that all of the VERs in the zap; match your dump of the module.
9. If the CA Disk SVC number you are using is not the default of 244 (x'F4'), you must now adjust the zaps to be sure they execute the correct SVC; for example, for SVC 245, change 0AF4 to 0AF5 within the body of the zap itself.
10. In the USERMOD column of the preceding table corresponding to your system level is the name of a member in the installation library. You can use this member as sample JCL to SMP/E install the IBM zap. This JCL installs a usermod onto your operating system.
11. IPL the system to load the modified IBM modules and the CA Disk SVC into storage. For MVS, do an MLPA or CLPA to initialize the link pack area.