A fix is available
APAR status
Closed as program error.
Error description
Setting up Job Log Monitoring for several resources. Forgot to set the Job Log Monitoring interval for one of the resources, but received msgING350I Improper Job Log Monitoring definition found for xxx RSN=14 for resources that were set up correctly with JLM.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All SA z/OS V3R4 customers using the Joblog * * Monitoring function. * **************************************************************** * PROBLEM DESCRIPTION: MsgING350I is issued when Job Log * * monitoring definitions exist but no * * Job Log Monitor Interval is specified. * * The same message can also be issued * * when the definitions are found * * in an application class. * **************************************************************** * RECOMMENDATION: * **************************************************************** Job Log Monitoring definitions should be ignored when no Job Log Monitor Interval is specified. Job Log Monitoring definitions should be processed correctly for application classes without issuing msgING350I with RSN=14.
Problem conclusion
REXX part INGRJLMP has been modified to correctly process Job Log monitoring information. +------ System Automation for z/OS Version 3 Release 4 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: Programmer's Reference SC34-2650-00 | | | |Chapter 2. SA z/OS System Operations Commands | |Topic: INGJLM | |Subtopic: Restrictions and Limitations | | | |Change: | |At the beginning of the subtopic, add the following: | | | | Dynamically allocated spool output data sets are not | | supported. | | | +--------------------------------------------------------------+ +------ System Automation for z/OS Version 3 Release 5 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: Programmer's Reference SC34-2748-00 | | | |Chapter 2. SA z/OS System Operations Commands | |Topic: INGJLM | |Subtopic: Restrictions and Limitations | | | |Change: | |At the beginning of the subtopic, add the following: | | | | Dynamically allocated spool output data sets are not | | supported. | | | +--------------------------------------------------------------+ ================================================================ +------ System Automation for z/OS Version 3 Release 4 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: Customizing and Programming SC34-2644-00 | | | |Chapter 5. Joblog Monitoring | |Topic: Overview | |Subtopic: Limitations | | | |Change: | |Add the following to the subtopic: | | | | 3. Dynamically allocated spool output data sets are not | | supported. | | | |--------------------------------------------------------------| | | |Topic: Overview | | | |Change: | | After the existing text: | | The monitoring function is controlled by SA z/OS based on the| | definitions of the customization dialog. | | | |Add the following: | | | | Monitoring is automatically started when the job reaches a | | status of UP, ACTIVE or RUNNING. When your job was already | | active at the time you specified the joblog monitoring | | definitions in the customization dialogs then this job must | | be restarted in order to start joblog monitoring for it. | | | +--------------------------------------------------------------+ ================================================================ +------ System Automation for z/OS Version 3 Release 5 --------+ | | |PROGRAM NUMBER: 5698-SA3 | | | |TITLE: Customizing and Programming SC34-2715-00 | | | |Chapter 5. Joblog Monitoring | |Topic: Overview | |Subtopic: Limitations | | | |Change: | |Add the following to the subtopic: | | | | 3. Dynamically allocated spool output data sets are not | | supported. | | | |--------------------------------------------------------------| | | |Topic: Overview | | | |Change: | | After the existing text: | | The monitoring function is controlled by SA z/OS based on the| | definitions of the customization dialog. | | | |Add the following: | | | | Monitoring is automatically started when the job reaches a | | status of UP, ACTIVE or RUNNING. When your job was already | | active at the time you specified the joblog monitoring | | definitions in the customization dialogs then this job must | | be restarted in order to start joblog monitoring for it. | | | +--------------------------------------------------------------+
Temporary fix
Comments
APAR Information
APAR number
OA46071
Reported component name
SYSTEM AUTO Z/O
Reported component ID
5698SA300
Reported release
340
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2014-09-17
Closed date
2014-11-17
Last modified date
2014-12-01
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UA75457 UA75458
Modules/Macros
INGRJLMP
| SC34265000 | SC34274800 | SC34264400 | SC34271500 |
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":"340","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
01 December 2014