A fix is available
APAR status
Closed as new function.
Error description
Small Enhancements . Misplaced data in PDB report for ADF APPLICATION INFO should not be grouped in with THRESHOLDS. . CICS messages are still displayed when deselecting component CICS from +SA_PREDEFINED_MSGS.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All SA z/OS V3R3 and V3R4 customers. * **************************************************************** * PROBLEM DESCRIPTION: see description below... * **************************************************************** * RECOMMENDATION: * **************************************************************** SA 3.3 & SA 3.4: o During ACF build of a system of type VM, data from a previously built system of type MVS is erroneously included in the VM system's ACF fragment. To avoid this, all variables from table AOFENSET need to be cleared before skeleton processing starts. o Check for a non-zero RC from the WTO command to avoid msgAOF760E NOVALUE CONDITION TRAPPED IN INGRYRU0 during INGREQ command with option VERIFY=WTOR. SA 3.4: o Allow threshold value of zero for DSNJ111E recovery. There is special automation code in ISSUEACT which handles msgDSNJ111E (All active Log data sets full). The defined action is only triggered when the message has appeared a certain number of times in a specified period of time. It does not allow to trigger the action at the first appearance of the message since a value of 0 could not be specified in field 'Log Alert Threshold' in policy DB2 CONTROL of entry type APL. o When Job Log Monitoring was suspended by System Automation then the 'START TASK=INGTJLM' command should be issued automatically after receiving msgDWO154I. o Within entry type MVC, policy PREDEFINED MESSAGES, the number of predefined messages can be tailored via component selections. When component CICS is deselected then erroneously the CICS-messages are still displayed in the message list of entry type MSG, policy MESSAGE AUTOMATION. Note that the build itself is correct and the messages are excluded from the AT. o In the PDB report, the section under ADF - APPLICATION DEFAULTS should not list data from the APPLICATION INFO policy (for instance, Shutdown Pass Interval, Start Delay, etc.) in the subsection for the THRESHOLDS policy. o INGLIST (INGRYST0) should avoid potential REXX syntax errors when processing parameters returned by exit AOFEXC05. o Reship KAHATR and KAHCAT to indicate correct level of SA. o The Automation Status change of an APG should only be allowed to Internal. o Clarify INGENVSA by removing VSAM from VQ2. o The INGMDFY command should no longer refer to the ACF SAVE command. o Clarify that AOFEXINT is not only called during IPL or RECYCLE. o Implement several INGRDS enhancements - for more information, refer to this link: https://ibm.biz/BdEHwQ o Enhance msgAOF350E with an additional Error Type/Code of 36/380. o Enhance the System Programmer Response for msgINGY1326I. o Enhance msgHSAL1105E.
Problem conclusion
Temporary fix
Comments
Changes have been made to implement the enhancements listed above. +------ System Automation for z/OS Version 3 Release 4 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC34-2649-00 | | Operator's Commands | | | |CHAPTER 2.0 SA z/OS System Operations Commands | |TOPIC 2.1 System Operations Commands | |SUB-TOPIC 2.1.53 INGMDFY | | | |CHANGE: | | | | Delete the following bullet from the 'Restrictions and | | Limitations': | | | | o ACF SAVE | | Saves the currently loaded, modified ACF data using the | | NetView SAVE facility. When restoring the saved data via | | ACF WARM, an existing KEEP is deleted. | | | |--------------------------------------------------------------| | | |CHAPTER 2.0 SA z/OS System Operations Commands | |TOPIC 2.1 System Operations Commands | |SUB-TOPIC 2.1.50 INGINFO | | | |CHANGE: | | | | Add the following Note at the end of this sub-topic | | (replacing the Note added by OA45381): | | | | NOTE: For groups, you may see 'Failed : Yes' under | | heading 'Group Details...'. This Group Failed flag is set | | when any member of the group (Basic, Move or Server) enters a| | HardDown state (CTLDOWN, BROKEN, STOPPED). The flag will not | | be cleared automatically by a subsequent successful (re)start| | of the APG's members. It remains set until manually cleared. | | Its sole purpose is to support the | | MakeAvailable/passive/WhenGroupHasNotFailed relationship. | | The usage is for situations where the (re)start of a | | dependent resource must be prevented until a certain | | recovery-related action has been performed. | | There are two ways to manually clear the flag: | | (1) via the INGSET command (INGSET SET resource GRPFAILED=NO)| | (2) via option 'A Update' from the INGLIST command. On panel | | INGKYST1, the group failed flag can be manipulated under | | '5. Set Group failed flag ___ (Yes or No)'. | | | |--------------------------------------------------------------| | | |CHAPTER 2.0 SA z/OS System Operations Commands | |TOPIC 2.1 System Operations Commands | |SUB-TOPIC 2.1.53 INGMDFY | | | |CHANGE: | | | | Under heading 'Restrictions and Limitations', delete the | | following bullet: | | | | o ACF SAVE | | Saves the currently loaded, modified ACF data using the | | NetView SAVE facility. When restoring the saved data via | | ACF WARM, an existing KEEP is deleted. | | | +--------------------------------------------------------------+ +------ System Automation for z/OS Version 3 Release 4 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC34-2646-00 | | Defining Automation Policy | | | |CHAPTER 4.0 Entry Type Reference | |TOPIC 4.8 Application Entry Type | |SUB-TOPIC 4.8.22 Policy Items for DB2 Subsystems | |HEADING: 4.8.22.1 DB2 CONTROL Policy Item | | | |CHANGE: | | | | In Figure 140, replace | | Log Alert Threshold . . . (1 to 99) | | with: | | Log Alert Threshold . . . (0 to 99) | | | |CHANGE: | | | | Under the explanation of 'Log Alert Threshold', add the | | following sentence: | | | | If 0 is specified, the specified command is issued on the | | first occurrence of the DSNJ111E message. | | | +--------------------------------------------------------------+ +------ System Automation for z/OS Version 3 Release 4 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: System Automation for z/OS SC34-2648-00 | | Messages and Codes | | | |CHAPTER 2.0 Messages AOF000I to AOFS820I | |TOPIC 2.220 AOF350E | | | |CHANGE: | | | | Insert the following entry into the error code table: | | | | | 36 | 380 | Explanation | | | | | An abend occurred. | | | | | RET describes the system or user completion | | | | | code of the abend. | | | | | RSN describes the reason code of the abend. | | | | | | | | | | Action | | | | | For the meaning of system completion code and | | | | | reason code see z/OS manual for system code. | | | | | The user completion code may be described in | | | | | Language Environment Messages manual or in | | | | | other z/OS components. | | | | | See also for additional error messages from | | | | | other z/OS components. For example message | | | | | CEE5101C might be issued if you missed to | | | | | assign an OMVS segment to the user id. | | | |--------------------------------------------------------------| | | |CHAPTER 9.0 Messages ING001I to INGY1326I | |TOPIC 9.480 INGY1326I | | | |CHANGE: | | | | Replace the System Programmer Response with the following: | | | | System Programmer Response: Determine the reason why the job| | id is not available. After the task DSIRQJOB has received a | | job id again (refer to message DWO154I) the task INGTJLM is | | automatically restarted. | | | | | |--------------------------------------------------------------| | | |CHAPTER 6.0 Messages HSAH001I to HSAL6288I | |TOPIC 6.20 HSAL1105E | | | |CHANGE: | | | | Replace msgHSAL1105E with the following: | | | | HSAL1105E IO OPERATION ON THE TAKEOVER FILE FAILED. | | REASON: diag_info | | | | Explanation: | | | | The automation manager failed to access or use the takeover | | file. The variable diag_info contains further details. | | | | diag_info = "DSN=xxxxx: ALLOC ERROR nnnn RC=rr RSN=ssss" | | | | The automation manager tried to allocate or deallocate the | | takeover file xxxxx. If a dynalloc error occurs the variable | | diag_info provides an error code and the dynalloc return and | | reason code. | | Meaning of alloc or dealloc error codes | | n008 invalid dataset or member or dd-name | | n012 dynalloc error | | n016 open error | | n020 internal error | | where n=1 means allocate and n=2 means deallocate. | | Example: | | diag_info = "ALLOC ERROR 1012 RC=4 RSN=1056" | | means allocation of the takeover file failed because | | takeover file is already open. | | | | For more details about dynalloc return and reason code refer | | to MVS Authorized Assembler Services Guide Chapter 26 | | "Interpreting DYNALLOC Return Codes". | | | | For other types of diag_info see following description: | | The automation manager tried to write or update the takeover | | file. A file operation function failed. | | | | o DSN= is the name of the takeover file. | | | | o The variable diag_info provides the following information| | about the error: | | | | C library function The file operation function that | | failed, for example, fopen. | | | | C library error code The error code issued by the file | | operation function (errno). | | | | C library error message The error message text provided | | by the failing file operation function. | | | | For more details about errno for C/C++ library functions see | | z/OS XL C/C++ Library Reference. | | | | System Action: | | | | The automation manager continues running. | | | | Operator Response: | | | | Check for I/O error messages and notify your system | | programmer. | | | | System Programmer Response: | | | | Perform a cold or warm start. Note that the automation | | manager must not perform a hot-start or takeover, because the| | takeover file may be damaged or contain old data. | | | +--------------------------------------------------------------+
APAR Information
APAR number
OA45488
Reported component name
SYSTEM AUTO Z/O
Reported component ID
5698SA300
Reported release
340
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-06-23
Closed date
2014-10-08
Last modified date
2014-11-04
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA75087 UA75088 UA75089 UA75090
Modules/Macros
AOFEXINT AOFFBSYS AOFFVTDC AOFFZTBL AOFGXCPY AOFHDXL AOFRAAT1 AOFRACF0 AOFTLP1 AOF35 HSAL110 HSAPICBK HSAPIEHM HSAPIEHX HSAPIEVS HSAPINIT HSAPISCO HSAPISLE HSAPISRV HSAPXAPI HSAPXCOM HSAPXCPP HSAPXRUN HSAPYQMA HSAPYTAS HSAPYTCP HSAPYTMA HSAPYXIT ING#MDFY ING#RDS INGENVSA INGH$IN INGMSGSA INGPAUTH INGPCGLB INGPCGLX INGPCTS1 INGPNJLM INGPXABX INGPXAPI INGPXDSR INGPXGRP INGPXGRX INGPXIAL INGPXIBL INGPXILL INGPXIMQ INGPXIMV INGPXIPI INGPXIPK INGPXIPO INGPXIRP INGPXISY INGPXISZ INGPXLCY INGPXMEM INGPXMSG INGPXMSQ INGPXRPC INGPXRUN INGPXSND INGPXTEX INGPXTRM INGPXUTI INGRCMDH INGRCRDS INGRCRDX INGRCVAC INGRCVAL INGRYRQ1 INGRYRU0 INGRYSE0 INGRYST0 INGRYST1 INGY132 ING33 ING34 KAHATR KAHCAT
| SC34264900 | SC34264600 | SC34264800 |
Fix information
Fixed component name
SYSTEM AUTO Z/O
Fixed component ID
5698SA300
Applicable component levels
R330 PSY UA75088
UP14/10/23 P F410
R34T PSY UA75087
UP14/10/22 P F410
R340 PSY UA75089
UP14/10/22 P F410
R341 PSY UA75090
UP14/10/22 P F410
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":"340","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
04 November 2014