Vary Configuration exit programs


  Required Parameter Group:

 Exit Point Name:  QIBM_QDC_VRYEXIT

 Exit Point Format Name:  PRON0100
 Exit Point Format Name:  PROF0100

 QSYSINC Member Name: EDCVARY

  Required Parameter Group:

 Exit Point Name:  QIBM_QDC_VRYEXIT

 Exit Point Format Name:  PSON0200
 Exit Point Format Name:  PSOF0200

 QSYSINC Member Name: EDCVARY

The QIBM_QDC_VRYEXIT exit point is defined to run all exit programs for which the program data indicates the object type and configuration type match the object being varied on. This exit point supports an unlimited number of exit programs.

Notes:

  1. The vary configuration exit points ignore any error messages that are sent from the user exit program.
  2. It is strongly recommended that the exit program reside within the system base or a user ASP.
  3. When a forced vary off has been issued the exit program's ability to reject the vary off processing is revoked and all user exit programs will be executed.
  4. When a vary request is made for a NWSD server connection type of *WINDOWSNT, *IXSVR, or *ISCSI the ability to reject the vary request is revoked and all user exit programs will be executed.
  5. When an Auxiliary Storage Pool (ASP) device that is part of a group is passed to the vary configuration (VRYCFG) command all ASP devices that are part of the group are varied, but the exit programs registered for an ASP device will be called only once for all ASPs in the group. The name of the object passed to the exit program in the object name field of the format will be the name of the object passed to the vary configuration command.
  6. If a preprocesing exit program rejects a vary on/off process any subsequent preprocessing programs will not be invoked, unless the forced vary off option is selected.
  7. If a preprocessing exit program rejects a vary on/off process all post processing exit programs will be invoked.
  8. Exit program processing is not supported for IPL online processing.
  9. Exit program processing is not supported for the console controller.
  10. Exit program processing is not supported for the console device.
  11. Exit program processing is not supported for auto configuration processing.
  12. Exit program processing is not supported for Power Down System (PWRDWNSYS).
  13. Exit program processing is not supported for vary requests made under system profiles.
  14. Exit program processing is not supported for vary request made from system jobs.

Authorities and Locks

The user must have *ALLOBJ to add or remove exit programs to the registration facility.


Required Parameter Group

Vary information
Input; CHAR(*)

The vary information associated with the current vary request. The format of the vary information is defined by the format name.

Return code
Output; BINARY(4)

The return value from the user exit program. If an undefined return code is returned, then the exit point will treat the return code as if it were 0.

NOTE: The return code parameter is only valid when processing exit point formats PRON0100 and PROF0100.

Vary Information formats

PRON0100 and PROF0100 Formats


PSON0200 and PSOF0200 Formats



Field Descriptons

Format name. The user exit format name being used. For QIBM_QDC_VRYEXIT, the format name is one of the following:

Forced vary. The field to indicate to the user exit program that a forced vary off is occurring.

Object name. The name of the object being processed by the vary configuration command (VRYCFG).

Object type. The type of object the exit program should be executed against. The following values are supported:

Status. The field value indicating if a preprocessing exit program rejected the vary request or the vary request was not successful.

Program Data. When registering the exit program 8 characters of program data must be passed. The first 4 characters are the object type and the remaining 4 characters should be the object configuration type.

Note: The configuration type value is dependent on the value specified for the object type.

Supported configuration types for object type DEVD


Supported configuration types for object type CTLD


Supported configuration types for object type LIND


Supported configuration types for object type NWSD

Notes: For compatibility purposes, user exit programs registered in V5R3 with NWSD configuration type WDNT will be processed as if IXSV had been specified.




Exit program introduced: V5R3

[ Back to top | Configuration APIs | APIs by category ]