|
- Description:
- Checks if the customer environment is capable of supporting an
AutoIPL policy and if it is, determines whether the AutoIPL policy
is active.
- Reason for check:
- IBM® suggests that you define
the AutoIPL policy using the DIAGxx parmlib member to minimize z/OS® system downtime. AutoIPL can
re-IPL MVS™, take a Stand Alone
Dump (SADMP), or take a SADMP and have SADMP re-IPL MVS when it has finished.
AutoIPL function
requires the Program-Directed IPL feature. AutoIPL is not appropriate
in GDPS® environment. If the
check determines that the customer does not have the hardware feature
or that the AutoIPL policy is not active, the check stops running.
- z/OS releases the check
applies to:
- z/OS V1R11
- User override of IBM values:
- The following shows the default keywords for the check, which
you can override on either a POLICY statement in the HZSPRMxx parmlib
member or on a MODIFY command. This statement may be copied and modified
to override the check defaults:
UPDATE
CHECK(IBMSVA,SVA_AUTOIPL_DEFINED)
ACTIVE
SEVERITY(MED) INTERVAL(24:00) DATE('date_of_the_change')
REASON('Your reason for making the update.')
- Parameters accepted:
- No.
- Reference:
- Debug support:
- No
- Verbose support:
- No
- Messages:
- This check issues the following exception messages:
See z/OS MVS System Messages, Vol 3 (ASB-BPX).
- SECLABEL recommended for multilevel security users:
- SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for
information on using SECLABELs.
- Output:
- The following report is generated by the SVA_AUTOIPL_DEV_VALIDATION
check when the device validation fails for devices specified in the
AutoIPL policy:
AutoIPL Device Error
action Address Description
------- --------- -----------------------------------------------------------
SADMP 03A0 Device is not DASD
In the output:
AutoIPL action = The AutoIPL action (SADMP or MVS).
Device Address = The address of the device failing the device validation.
Error Description = The description of the problem
|