IBM Support

OA46674: SMALL ENHANCEMENTS

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as new function.

Error description

  • Small Enhancements
    Additional symptoms:
    Abend0C4 in IHVDPSC at offset +x'3A8' register 4 invalid.
    Called from IHVACLN +x'328' register 1 parms point to SWIT
    control block.
    
    PRIORITY color values must have precedence over DCOLOR in
    AOFINIT.
    Data in AOFINIT in columns 73-80 should be ignored and not
    produce msgAOFS501I.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All SA z/OS V3R3, V3R4 and V3R5 customers.   *
    ****************************************************************
    * PROBLEM DESCRIPTION: see description below...                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    SA 3.3, 3.4 & SA 3.5:
    o HSAL1406I SERVICE PERIOD TIME SLOT HAS BEEN MISSED FOR
    resource can be issued when a Service Period defined in the
    policy is blanked out.
    
    SA 3.4 & SA 3.5:
    o When editing an RDS tables using INGRCRDX and attempting to
    illegally delete a table field (table control header),
    then msgING332I Command execution failed RC=12 is issued.
    The content of the table should not be lost.
    o The INGLKUP help panel should explain where the possible
    values for Job Type can be found.
    o An ACF COLD command should not delete the AOF.0SDF.* cglobals.
    o Use SCREENSZ values from AOFINIT when size values are not
    passed on the SDFPANEL command via rows/cols values.
    o HSAL1110I should not be truncated.
    o Enhance INGSTGEN and sample PDB AOFJPDBD to support GDPS 3.12
    and GDPS/MTMM.
    
    SA 3.5:
    o Extend 'Monitor for IPL complete' from status AVAILABLE to
      SOFTDOWN, STANDBY and SATISFACTORY.
    o The following messages have been added to the
    +SA_PREDEFINED_MSGS:
    CAZL003I IBM APA z/OS Listener terminating to trigger
    TERMMSG FINAL=NO
    and
    CAZL023I IBM APA z/OS PDTCC is available to trigger
    ACTIVMSG UP=YES
    o Clarify when INGMSGGP is automatically loaded.
    o Clarify the meaning of External Shutdown FINAL and
    Monitor Interval.
    o Clarify the implication/restriction when the task in the
    timer definition is changed. The 'old' timers running under
    the 'old' task remain in effect until manually purged.
    o MsgDFS3626I has been added to the *IMS add-on policy.
    o Batch report sample job INGEBRP2 has been clarified to
    indicate that for the ISPSTART command, the DD-name (parm 6)
    is only required for option 'M' (Unused member list).
    o Sample INGCMD has been updated to enhance the syntax for
    GDPS Active/Active Satellite support.
    o Sample AOFAUTB has been updated to enhance the syntax.
    o Messages ING313I, ING314I and ING315I have been enhanced.
    o The explanation of the INGAUTO command has been improved.
    o Sample IHVMTX has been corrected to remove a duplicate 'Then'
    in the syntax.
    o The sort algorithm in IHVBSRT has been fixed to prevent a
    potential 0C4 in IHVDPSC.
    o Make sure that PRIORITY color values take precedence over
    DCOLOR in AOFINIT.
    o Data in AOFINIT in columns 73-80 should be ignored and not
    produce msgAOFS501I.
    o The help for msgING164I has been improved.
    o The monitor routine for the Looping Address Space Suppression
    (INGROMLS) has been enhanced.
    o When user data exist for a predefined message in the PDB then
    the user data should not be displayed when looking at the
    predefined data in +SA_PREDEFINED_MSGS.
    

Problem conclusion

Temporary fix

Comments

  • Changes have been made to implement the enhancements listed
    above.
    +------ System Automation for z/OS Version 3 Release 5 --------+
    |TITLE:       System Automation for z/OS         SC34-2716-00  |
    |             Planning and Installation                        |
    |CHAPTER      10. Traditional SA z/OS Configuration            |
    |TOPIC:       Step 35: Configuring GDPS                        |
    |SUBTOPIC:    Step 35A: Preparing NetView                      |
    |CHANGE:                                                       |
    | Under item (3), remove the text beginning with 'Additionally |
    | specify the GDPS product of your installation...' and the    |
    | list of TOWER.SA statements. Replace all this with the       |
    | following text:                                              |
    |                                                              |
    | For a list of valid gdps-option statements, refer to the     |
    | the INGSTGEN member from the sample library.                 |
    |--------------------------------------------------------------|
    |TOPIC:       Step 35:  Configuring GDPS                       |
    |SUBTOPIC:    Step 35C: Defining the Automation Table Used by  |
    |                       GDPS                                   |
    |CHANGE:                                                       |
    | Replace the existing Note, beginning with 'If the TOWER.SA   |
    | statement...' and ending with '...the list of automation     |
    | tables.' with the following text:                            |
    |                                                              |
    | Note: If the TOWER.SA statement includes GDPS or GDPSSAT, or |
    | the TOWER.ACTIVEACTIVE statement includes LIFELINE, the      |
    | INGMSGGP automation table that is required by each supported |
    | GDPS is automatically loaded during initialization of        |
    | SA z/OS. This is ONLY the case if no user-defined automation |
    | table is specified in the system's SYSTEM INFO in the        |
    | customization dialog.                                        |
    | If any user-defined automation table is specified, you should|
    | also add INGMSGGP to the list of automation tables if you    |
    | want it to be loaded automatically.                          |
    +--------------------------------------------------------------+
    +------ System Automation for z/OS Version 3 Release 5 --------+
    |TITLE:       System Automation for z/OS         SC34-2717-00  |
    |             Defining Automation Policy                       |
    |CHAPTER      4. Entry Type Reference                          |
    |TOPIC:       System Defaults Entry Type                       |
    |SUBTOPIC:    AUTOMATION OPTIONS Policy Item                   |
    |CHANGE:                                                       |
    |                                                              |
    | Figure 209. System Automation Options Panel has the following|
    | new field after 'IPL Complete Time Limit':                   |
    |                                                              |
    | IPL Complete Status  . . : __________________________        |
    |                                 (AVAILABLE SOFTDOWN STANDBY) |
    |                                 (or SATISFACTORY)            |
    |                                                              |
    | After the description of 'IPL Complete Time Limit', add the  |
    | the following:                                               |
    |                                                              |
    | IPL Complete Status                                          |
    |    Defines a list of observed statuses the resources may have|
    |    to consider the IPL to be completed.                      |
    |    Valid values are AVAILABLE, STANDBY and SOFTDOWN.         |
    |    One or more values are allowed to be specified.           |
    |    Instead of a list of observed statuses the compound status|
    |    SATISFACTORY may be specified.                            |
    |    Note: If nothing is specified the default value is        |
    |    AVAILABLE.                                                |
    |--------------------------------------------------------------|
    |CHAPTER      4. Entry Type Reference                          |
    |TOPIC:       System Entry Type                                |
    |SUBTOPIC:    SYSTEM INFO Policy Item                          |
    |CHANGE:                                                       |
    |                                                              |
    | Under heading 'Automation Table(s)' add the following at the |
    | end of the existing text:                                    |
    |                                                              |
    | Note: If one or more user-defined automation tables are      |
    | specified, only those will automatically be loaded during    |
    | initialization.                                              |
    | Therefore make sure that SA z/OS supplied automation tables  |
    | (e.g. INGMSG01 or INGMSGGP) are included in the list if those|
    | should also be loaded.                                       |
    |--------------------------------------------------------------|
    |CHAPTER      4. Entry Type Reference                          |
    |TOPIC:       Application Entry Type                           |
    |SUBTOPIC:    APPLICATION INFO Policy Item                     |
    |CHANGE:                                                       |
    |                                                              |
    | Under heading 'External Shutdown', add the following to the  |
    | end of the explanation of 'FINAL':                           |
    |                                                              |
    | Restriction:                                                 |
    | A parent is only considered being stopped if any existing    |
    | PREPUNAVAILABLE relationships are fulfilled and the          |
    | SHUTINIT commands have been run.                             |
    |--------------------------------------------------------------|
    |CHANGE:                                                       |
    |                                                              |
    | Under heading 'Monitor Interval', add the following to the   |
    | end of the explanation:                                      |
    |                                                              |
    | This will also prevent inheritance.                          |
    | Note: If the monitor routine is NONE, any value specified    |
    | here is not honored. It is forced to NONE.                   |
    |--------------------------------------------------------------|
    |CHAPTER      4. Entry Type Reference                          |
    |TOPIC:       Timers Entry Type                                |
    |SUBTOPIC:    TIMERS Policy Item                               |
    |CHANGE:                                                       |
    |                                                              |
    | Under heading 'Task', replace the existing text with the     |
    | following:                                                   |
    | Task                                                         |
    | Specify the automated function or NetView task name where the|
    | command should run. You may also specify a NetView operator  |
    | group by using a '+' sign as first character (e.g. +OPERGRP).|
    | To run under the primary programmed task (PPT) specify PPT . |
    | Be aware that not all commands can run under the PPT.        |
    | Restriction: If the task in the timer definition is changed  |
    |              the timers existing under the old task cannot   |
    |              be purged during an INGAMS REFRESH processing.  |
    |              The changed timers are added as new ones and the|
    |              old timers remain in effect until manually      |
    |              purged.                                         |
    +--------------------------------------------------------------+
    +------ System Automation for z/OS Version 3 Release 5 --------+
    |TITLE:       System Automation for z/OS         SC34-2718-00  |
    |             User's Guide                                     |
    |CHAPTER      7. How to Monitor and Control Resources          |
    |TOPIC:       Monitoring for IPL Completion                    |
    |CHANGE:                                                       |
    |                                                              |
    | After the existing text:                                     |
    |                                                              |
    | This process checks whether the selected Application         |
    | Group(s), Application(s) or Monitor Resource(s) have reached |
    | the status of AVAILABLE within the specified time limit, and |
    | the IPL is indicated as 'successfully completed'.            |
    |                                                              |
    | add the following:                                           |
    |                                                              |
    | Alternatively, an IPL Complete Status of STANDBY, SOFTDOWN or|
    | the compound status SATISFACTORY can be specified in the     |
    | System Defaults policy.                                      |
    +--------------------------------------------------------------+
    +------ System Automation for z/OS Version 3 Release 5 --------+
    |TITLE:       System Automation for z/OS         SC34-2719-00  |
    |             Messages and Codes                               |
    |CHAPTER      10. Messages ING001I to INGY1326I                |
    |TOPIC:       ING313I                                          |
    |CHANGE:                                                       |
    | Replace the Explanation with the following:                  |
    |                                                              |
    | Explanation:                                                 |
    | IPL completed within the expected time period. This means all|
    | required resources have reached one of the specified         |
    | statuses. The specified statuses are shown in DISPSYS. This  |
    | message will only be reported on the console.                |
    |                                                              |
    | Replace the explanation for variable duration with the       |
    | following:                                                   |
    |                                                              |
    | Variable duration shows the time it took all required        |
    | resources to reach one of the specified statuses.            |
    |                                                              |
    |TOPIC:       ING314I                                          |
    |CHANGE:                                                       |
    |                                                              |
    | Replace the Explanation with the following:                  |
    |                                                              |
    | Explanation:                                                 |
    | IPL did not complete within the maximum time limit. This     |
    | means not all required resources have reached one of the     |
    | specified statuses. The specified statuses are shown in      |
    | DISPSYS. The failing resources are appended to the above     |
    | message test. This message will only be reported on the      |
    | console.                                                     |
    |                                                              |
    | Replace the explanation for variable resource with the       |
    | following:                                                   |
    |                                                              |
    | Variable resource displays the names of all resources which  |
    | have not reached one of the specified statuses.              |
    |                                                              |
    | Replace the Operator Response with the following:            |
    |                                                              |
    | Operator Response:                                           |
    | Check the failing resources and correct the problem(s) which |
    | are blocking the resources to reach one of the specified     |
    | statuses.                                                    |
    |                                                              |
    |TOPIC:       ING315I                                          |
    |CHANGE:                                                       |
    | Replace the Explanation with the following:                  |
    |                                                              |
    | Explanation:                                                 |
    | IPL completed after the expected time period. This means all |
    | required resources have finally reached one of the specified |
    | statuses but not within the expected time period.            |
    | The specified statuses are shown in DISPSYS. This message    |
    | will only be reported on the console.                        |
    |                                                              |
    | Replace the explanation for variable duration with the       |
    | following:                                                   |
    |                                                              |
    | Variable duration shows the time it took all required        |
    | resources to reach one of the specified statuses.            |
    |--------------------------------------------------------------|
    |CHAPTER      10. Messages ING001I to INGY1326I                |
    |TOPIC:       ING164I                                          |
    |CHANGE:                                                       |
    | Replace the explanation for reason 0004xyyy with the         |
    | following:                                                   |
    | 0004xyyy  An HTTP error occurred while processing the        |
    |           request. If x=0, yyy denotes the 3-digit HTTP      |
    |           response code, for example, 404.                   |
    |           If x=1 and y=008 check userID and password         |
    |           otherwise the variable yyy represents the internal |
    |           error code.                                        |
    +--------------------------------------------------------------+
    +------ System Automation for z/OS Version 3 Release 5 --------+
    |TITLE:       System Automation for z/OS         SC34-2720-00  |
    |             Operator's Commands                              |
    |CHAPTER      2. System Operations Commands                    |
    |TOPIC:       INGAUTO                                          |
    |CHANGE:                                                       |
    |                                                              |
    | Replace the 'purpose' with the following text:               |
    |                                                              |
    | Purpose                                                      |
    | The INGAUTO command lets you change the settings of the      |
    | automation flags for the specific subsystem, for the MVSESA, |
    | SUBSYSTEM or DEFAULTS , resources or for a minor resource    |
    | under one of those major resources.                          |
    | You can change the setting to ON, OFF, EXITS or LOG. If an   |
    | INTERVAL is specified the changes are effective for the      |
    | specified time period.                                       |
    | Any changes will only be effective until a NetView recycle or|
    | an ACF COLD command being issued. You can also ask for a flag|
    | to be set back to the value specified in the current         |
    | configuration file.                                          |
    |                                                              |
    | Replace the description of parameter INTERVAL with the       |
    | following text:                                              |
    |                                                              |
    | INTERVAL=dd:hh:mm                                            |
    |   Specifies the period of time the flag will be changed for. |
    |   At the end of the interval, the flag is reset to the state |
    |   defined in the agent's configuration file.                 |
    +--------------------------------------------------------------+
    +------ System Automation for z/OS Version 3 Release 5 --------+
    |TITLE:  Programmer's Reference                  SC34-2748-00  |
    |                                                              |
    |CHAPTER      9. SDF Commands                                  |
    |TOPIC:       SDFPANEL                                         |
    |CHANGE:                                                       |
    | Replace the syntax diagram with the following:               |
    |   Syntax                                                     |
    |     To add or delete a panel member use the following        |
    |     syntax:                                                  |
    |                                                              |
    |  >>-SDFPANEL-.-panel_mbr-,-.-Add------.-.------------.-.-->< |
    |              |             '-DISKonly-' '-,rows,cols-' |     |
    |              '-panel_name-,-DELete---------------------'     |
    |                                                              |
    |CHANGE:                                                       |
    | Under heading 'Parameters', replace the description for      |
    | rows and cols with the following:                            |
    |                                                              |
    |   rows  The minimum number of rows. Values can range from 24 |
    |         to 62. The default is the corresponding value        |
    |         defined by the SCREENSZ parameter in the member      |
    |         AOFINIT.                                             |
    |   cols  The minimum number of columns. Values can range from |
    |         80 to 160. The default is the corresponding value    |
    |         defined by the SCREENSZ parameter in the member      |
    |         AOFINIT.                                             |
    +--------------------------------------------------------------+
    

APAR Information

  • APAR number

    OA46674

  • 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-12-02

  • Closed date

    2015-04-02

  • Last modified date

    2015-05-04

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UA76795 UA76796 UA76797 UA76798 UA76799 UA76800 UA76801

Modules/Macros

  • AOFAUTB  AOFDBFSR AOFDMINI AOFDMPPC AOFDPDDF AOFD22   AOFF#POL
    AOFF@MS1 AOFFBFL1 AOFFBFQ1 AOFFCPTF AOFFCREL AOFFFTMX AOFFLMSG
    AOFFSDFO AOFFTADV AOFFVTDB AOFFVTDC AOFFZTBL AOFGMATS AOFGSDFO
    AOFH$DIS AOFHLPA0 AOFHSDFO AOFHSPD0 AOFHXREL AOFJPDBD AOFJPDB7
    AOFPHTI0 AOFRACF0 AOFRACF7 AOFRADAE AOFRANT3 AOFRCFGC AOFRVDAE
    AOFSSDF  AOFTLP1  AOFT0CPD AOFT0MSA AOFT0MSX HSAAPIZZ HSACMAIN
    HSAPLGMC IHVBSRT  IHVMTX   ING#AUTO ING#MSGS INGCMD   INGEBRP2
    INGFIF12 INGFIF13 INGH$AIB INGH$LU  INGPCGLB INGPCGLX INGPXIMV
    INGRCRDS INGRCVAL INGRFTIM INGRFXIT INGROMLS INGRXTX0 INGSTGEN
    ING16    ING31    ING37
    

Publications Referenced
SC34271600SC34272000SC34271700SC34274800SC34271800
SC34264500SC34271900SC34265000  

Fix information

  • Fixed component name

    SYSTEM AUTO Z/O

  • Fixed component ID

    5698SA300

Applicable component levels

  • R330 PSY UA76795

       UP15/04/09 P F504

  • R340 PSY UA76796

       UP15/04/09 P F504

  • R341 PSY UA76799

       UP15/04/09 P F504

  • R35D PSY UA76797

       UP15/04/09 P F504

  • R35F PSY UA76800

       UP15/04/09 P F504

  • R350 PSY UA76798

       UP15/04/09 P F504

  • R351 PSY UA76801

       UP15/04/09 P F504

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 May 2015