z/OS DFSMSrmm Implementation and Customization Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


EDG_EXIT100 exit routine processing

z/OS DFSMSrmm Implementation and Customization Guide
SC23-6874-00

EDG_EXIT100 gets called at several points if DFSMSrmm does not already have the required information. For example, if the required information for the current data set and volume combination was provided in a previous call of the exit, EDG_EXIT100 is not called again. The points that EDG_EXIT100 can be called are as follows:
  • At pre-ACS processing time for new allocations, a pointer to the ACERO is passed in PL100_ACEROPTR.
  • At OPEN time in the address space of the program issuing the OPEN request. During OPEN processing the address of a copy of the JFCB is provided in PL100_JFCBPTR.

    EDG_EXIT100 can also be called at CLOSE or EOV if the information that DFSMSrmm requires for processing is not available. For example, EDG_EXIT100 can be called if DFSMSrmm is restarted while tape volumes are in use.

  • At CLOSE and EOV time in the address space of the program processing the tape file. PL100_ITS_CLOSE is set and PL100_LABINFO provides information useful for creating labels.
  • When DFSMSrmm updates a write to operator message defined by the EDGRMMxx parmlib MNTMSG command.

    You use the MNTMSG operands to identify the write to operator messages that you want DFSMSrmm to update with external volume serial number and pool information. Messages are processed for both specific and non-specific volume serial numbers. If the JES3 IATUX71 exit is used with the DFSMSrmm EDG3X71 exit, EDG_EXIT100 is called during JES3 fetch and mount message processing.

    EDG_EXIT100 can also be called from MSGDISP processing if the information that DFSMSrmm requires for processing is not available. For example, EDG_EXIT100 can be called if DFSMSrmm is restarted while tape volumes are in use.

DFSMSrmm has not yet checked if the volume is defined in its control data set, if the volume will be rejected, or if the volume is subject to any other DFSMSrmm processing.

After the installation exit has been called, DFSMSrmm performs this processing:
  • If the expiration date is updated by the exit, DFSMSrmm updates the date in the copy of the JFCB for the current request. DFSMSrmm does not update the real JFCB control block.
  • If a vital record specification management value is returned, DFSMSrmm records this value together with other details for the data set in the DFSMSrmm control data set, for use during inventory management.
  • During pre-ACS processing if a pool or vital record specification management value is returned, DFSMSrmm sets the MSPOOL and MSPOLICY variables into the ACERO if the pre-ACS installation exit IGDACSXT has not already done so.
  • If a specific pool name is returned and it meets the pool naming conventions, DFSMSrmm uses the value to update messages intercepted for MNTMSG processing, to update tape drive displays through MSGDISP processing and to perform pool validation of scratch volumes at OPEN time. If JES3 is used and IATUX71 is in use, the pool is also passed to JES3 for use in JES3 fetch and mount messages. If you request that DFSMSrmm prevents the tape drive cartridge loader from being indexed, DFSMSrmm resets the automatic cartridge load flag during MSGDISP processing. If the selected pool does not meet the naming conventions, DFSMSrmm uses the pool it has already selected.
  • If the volume must be ignored, DFSMSrmm ensures that the current user is authorized to request that DFSMSrmm ignores this volume. A SAF request is used to check authorization:
      RACROUTE REQUEST=AUTH,ENTITY=STGADMIN.EDG.IGNORE.TAPE.volser,
               ACCESS=value,LOG=ASIS
    where:
    volser
    Is the current volume serial number of the mounted volume
    value
    Is either READ or UPDATE

    If the user is authorized, DFSMSrmm ignores all further activity for this volume until end-of-volume processing or until a data set on the volume is closed. This means that DFSMSrmm does not validate that the correct volume is mounted, does not record volume usage in its control data set and cannot provide any management functions for the volume based on the data about to be created. However, if the user is authorized to ignore processing, this overrides any decision taken by RACF because of authorization in the DATASET class.(TAPEAUTHDSN=YES, or SETROPTS TAPEDSN). During OPEN processing for specific volume requests, DFSMSrmm overrides RACROUTE return codes of 4 or 8 so that they are return code 0. EDGUX100 can be tailored to prevent overriding of the RACROUTE return code 8, if PL100_SET_NOTBYPASS_SAFRC8 is set on.

    If authorization fails and DFSMSrmm is running in protect mode, DFSMSrmm rejects the volume. For non-specific mount requests, another volume is requested. For specific volume requests the OPEN request fails.

    If the resource does not exist, the request is treated as not authorized.

    If authorization fails and DFSMSrmm is running in record-only mode, DFSMSrmm ignores the volume and issues the information message, EDG4047I.

    If authorization fails and DFSMSrmm is running in warning mode, DFSMSrmm ignores the volume but issues error and warning messages.

  • If a rack number is returned, DFSMSrmm uses this value as if it were a normal DFSMSrmm rack number for use in messages that are updated as defined by the parmlib MNTMSG definitions.
  • DFSMSrmm validates the information you set in the parameter list as follows:
    PL100_VRS
    Must meet the z/OS data set naming standards for a single data set qualifier.
    PL100_RACKNO
    For specific volume requests, this value must be uppercase, alphanumeric, national, or special characters.
    PL100_POOL
    For non-specific volume requests the pool prefix must be uppercase, one to five alphanumeric, national, or special characters ending in *.
    PL100_LOCATION
    If the location type is set to store or library, DFSMSrmm uses the EDGRMMxx LOCDEF definitions to validate the location. If the location name is not valid, DFSMSrmm treats the location name as a loan location.
  • If you request no data set recording for a volume, DFSMSrmm updates the volume record during OPEN processing to identify that the volume does not record all data sets.
  • If you specify the DFSMSrmm EDGRMMxx OPTION DISPDDNAME operand, DFSMSrmm uses the location, location type, and volume move confirmation values from the PL100 parameter list to update the volume record location and destination fields. If you request "no confirm move", DFSMSrmm sets the location, otherwise DFSMSrmm sets the destination for the volume. If the location type is a loan location, DFSMSrmm only records the loan location.
  • When any exit module sets a non-zero return code, DFSMSrmm issues message EDG0313I. When any exit module abends, DFSMSrmm issues message EDG0314I. If an error occurs in CSVDYNEX at any point in processing, DFSMSrmm issues message EDG0312I. In all cases, mount message, SMS pre-ACS, and O/C/EOV processing continues.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014