A fix is available
APAR status
Closed as program error.
Error description
Additional documentation for command INGREQ PRECHECK
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All SA z/OS V3R5 customers. * **************************************************************** * PROBLEM DESCRIPTION: The explanation of the INGREQ PRECHECK * * parameter is no longer up-to-date and * * not detailed enough. * * * * There should be documentation to * * explain the implications when the * * automation manager sends an order to * * the automation agent and the agent * * finds the relevant automation flag * * to be turned off. * **************************************************************** * RECOMMENDATION: * **************************************************************** Documentation of the INGREQ PRECHECK parameter should be improved. The impact of automation agent flags on start/stop orders should be explained.
Problem conclusion
Panel ING#REQ has been modified to improve the description of the PRECHECK parameter. Documentation has been updated as described below. +------ System Automation for z/OS Version 3 Release 5 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC34-2720-00 | | Operator's Commands | | | |CHAPTER 2. System Operations Commands | |TOPIC INGREQ | | | |CHANGE: | | | | Under heading 'Parameters', for the PRECHECK parameter, | | replace this list: | | | | o START or STOP ability, depending on current status | | o Automation flag checks, depending on the request type | | o Extra feature (CICS or DB2) start or stop ability checks | | | | with the following new list: | | | | o START or STOP ability, depending on current status | | | | The automation manager will not order the start of a | | resource which is in a Harddown status. A check is | | performed to make sure that the resource is not in | | STOPPED, BROKEN or CTLDOWN. It is also checked to verify | | that the resource is not currently involved in an | | automated shutdown. For a stop request, a check is | | performed to verify that the resource is not currently | | involved in an automated startup. | | | | o Automation flag checks, depending on the request type | | | | Provided the global automation flag is on, for a start | | request, the initstart flag is checked when the resource | | is currently in DOWN status. For any other down state, | | the restart flag is checked. | | For a stop request, the terminate flag is checked. | | | | o Existence of start/stop commands | | | | A check is performed to make sure that definitions for | | the appropriate start or stop commands exist. | | | +--------------------------------------------------------------+ +------ System Automation for z/OS Version 3 Release 5 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC34-2718-00 | | User's Guide | | | |CHAPTER 2. Concepts | |TOPIC: SA z/OS Automation Flags | |SUBTOPIC: Automation Agent Flags | | | |CHANGE: | | | | Add the following note to the end of this subtopic: | | | | Note: | | When the automation agent receives a start or stop order | | from the automation manager, the agent will check the | | relevant automation agent flag before issuing the actual | | start or stop command for the resource. If automation is not | | allowed according to the flag setting, the automation agent | | will reschedule itself on a timer and re-check the flag | | setting. For a start request, the resource's Start Delay time| | is used for the timer rescheduling. For a stop request, the | | resource's Shutdown Pass Interval is used for scheduling | | the timer. | | This means, turning the relevant automation flag on while | | the automation agent has rescheduled itself will not | | immediately result in starting or stopping of the resource. | | The resource's start or stop commands will only be issued | | after the relevant timer expired. | | | +--------------------------------------------------------------+
Temporary fix
Comments
APAR Information
APAR number
OA51863
Reported component name
SYSTEM AUTO Z/O
Reported component ID
5698SA300
Reported release
350
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-01-05
Closed date
2017-01-13
Last modified date
2017-02-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA83789 UA83790
Modules/Macros
ING#REQ
| SC34272000 | SC34271800 |
Fix information
Fixed component name
SYSTEM AUTO Z/O
Fixed component ID
5698SA300
Applicable component levels
Fix is available
Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.
[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSWRCJ","label":"IBM Tivoli System Automation for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"350","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
01 February 2017