CA Workload Automation CA 7 Edtion CA RS 1606 Service List

Transcription

1 CA Workload Automation CA 7 Edtion CA RS 1606 Service List Description Type 11.3 RO89375 IDASH REJECTS EVENTS DUE TO INVALID INSTANCE ID PTF RO89563 CA-7 SERVER FOR IDASH SEED DATA EVENTS LACK LPAR ID PTF RO89651 CA-7 SERVER FOR IDASH S0C4 NEAR SUB CANCEL PTF RO89806 S0C7 IN SASSQM82 PTF RO89819 CA-7 SERVER FOR IDASH LISTJOBSTATUS DATA INCORRECT PTF RO89941 XPJOBS NOT TRACKING WITH XPHAO OPTION *HIP/PRP* RO90123 SASSHE06 - HISTORY 6 REPORT AND JOB COMP CODE PTF The CA RS 1606 service count for this release is 7

2 CA Workload Automation CA 7 Edtion 2 CA RS 1606 Service List for CAL2B30 FMID Service Description Type CAL2B30 RO89806 S0C7 IN SASSQM82 PTF RO89941 XPJOBS NOT TRACKING WITH XPHAO OPTION *HIP/PRP* RO90123 SASSHE06 - HISTORY 6 REPORT AND JOB COMP CODE PTF The CA RS 1606 service count for this FMID is 3

3 CA Workload Automation CA 7 Edtion 3 CA RS 1606 Service List for CAL2B31 FMID Service Description Type CAL2B31 RO89375 IDASH REJECTS EVENTS DUE TO INVALID INSTANCE ID PTF RO89563 CA-7 SERVER FOR IDASH SEED DATA EVENTS LACK LPAR ID PTF RO89651 CA-7 SERVER FOR IDASH S0C4 NEAR SUB CANCEL PTF RO89819 CA-7 SERVER FOR IDASH LISTJOBSTATUS DATA INCORRECT PTF The CA RS 1606 service count for this FMID is 4

4 CA Workload Automation CA 7 Edtion CA RS PTF RO RO89375 RO89375 M.C.S. ENTRIES = ++PTF (RO89375) IDASH REJECTS EVENTS DUE TO INVALID INSTANCE ID Once CA-7 Server for idash has monitored a single instance of CA7 for long enough, the unique event ID used to track events seen iterates into the high order byte of its field. When this occurs, it removes the unintended null terminator from the previous character field, which is the CA7 instance ID. This causes the event XML being sent to idash to contain invalid hex characters in the CA7 instance ID, which in turn, causes idash to reject that data. CA-7 Server for idash begins emitting the warning WTOs for event recovery constantly, for any subscriptions currently active. As soon as recovery completes, it begins again. The idash product also loses all CA7 tracking data, and fails to update any CA7 information, SLAs, etc. The CA-7 Server for idash task, and the ENF task, both begin to exhibit high CPU and memory consumption for extended periods of time. The mainframe tasks consume large amounts of CPU and memory, and any SLAs defined in idash all show the various forms of 'missed' status. Perform a Full Reset of both CA-7 Server for idash, and idash. This will reset the field involved in this problem, and allow idash to recover all missed data. CA Workload Automation SE Version Copyright (C) 2016 CA. All rights reserved. R00837-AL2113-SP1 DESC(IDASH REJECTS EVENTS DUE TO INVALID INSTANCE ID). FMID (CAL2B31) PRE ( RO51292 RO55213 RO67807 RO85842 RO87253 RO88201 ) SUP ( TR89375 )

5 CA Workload Automation CA 7 Edtion CA RS PTF RO RO89563 RO89563 M.C.S. ENTRIES = ++PTF (RO89563) CA-7 SERVER FOR IDASH SEED DATA EVENTS LACK LPAR ID New idash instance definitions that need seed data will be unable to parse the seed data events sent by CA-7 Server for idash due to a missing LPAR ID in the XML sent. This is only possible when there is no STATICNODE parameter set. Seed data generation messages seen in CA-7 Server for idash seem to begin again as soon as the current attempt ends. All subscriptions held by this CA-7 Server for idash also cycle through recovery constantly during the previous symptom. Small impact; only new subscriptions without previous seed data are able to trigger this issue. Parameter or manual circumvention is possible. Locate the IDASHAS parameter member and add a valid STATICNODE keyword. CA Workload Automation SE Version Copyright (C) 2016 CA. All rights reserved. R00838-AL2113-SP1 DESC(CA-7 SERVER FOR IDASH SEED DATA EVENTS LACK LPAR ID). FMID (CAL2B31) PRE ( RO67807 RO71985 RO72528 RO85842 ) SUP ( TR89563 )

6 CA Workload Automation CA 7 Edtion CA RS PTF RO RO89651 RO89651 M.C.S. ENTRIES = ++PTF (RO89651) CA-7 SERVER FOR IDASH S0C4 NEAR SUB CANCEL Failure to check the return value on any attempt to acquire a subscription mutex lock can lead to race conditions and abends. Especially in situations where a subscription is being repeatedly cancelled and resubscribing. The CA-7 Server for idash task will sometimes abend with a S0C4 code. The abend becomes more likely over time, and in direct proportion to the frequency of cancellation queries. Moderate: The CA-7 Server for idash task will abend unpredictably, as well as causing more frequent subscription recovery. This will cause severe increases in the CPU and memory consumed by the task. Ensure the entire idash system is conifgured properly in order to minimize the use of subscription cancellation. CA Workload Automation SE Version Copyright (C) 2016 CA. All rights reserved. R00839-AL2113-SP1 DESC(CA-7 SERVER FOR IDASH S0C4 NEAR SUB CANCEL). FMID (CAL2B31) PRE ( RO51292 RO55213 RO67807 RO83290 RO85842 RO87253 RO88201 ) SUP ( TR89651 )

7 CA Workload Automation CA 7 Edtion CA RS PTF RO RO89806 RO89806 M.C.S. ENTRIES = ++PTF (RO89806) S0C7 IN SASSQM82 CA7ONL abnormally terminates with a S0C7 abend after an AGFILE command was entered and a 'Spool Offset' is specified. This is a sporadic occurrence. CA7ONL receives a S0C7 abend in module SASSQM82. CA7ONL abnormally terminates and must be restarted. None Copyright (C) 2016 CA. All rights reserved. R00840-AL2113-SP1 DESC(S0C7 IN SASSQM82). FMID (CAL2B30) PRE ( RO30845 RO31843 RO55172 RO79313 ) SUP ( RO68305 TR68305 TR89806 )

8 CA Workload Automation CA 7 Edtion CA RS PTF RO RO89819 RO89819 M.C.S. ENTRIES = ++PTF (RO89819) CA-7 SERVER FOR IDASH LISTJOBSTATUS DATA INCORRECT The ListJobStatus query submitted by idash, after applying RO87252 and RO87253, provides the correct job data for the CA7 queues but with all jobs marked as "Waiting Workload" status instead of their true status. Any SLA defined in idash for a job in the CA7 Queues would fail to reflect a current run, and as a result, likely throw its SLA_PREDICTED_MISS alarm. Low: idash misses the current state of the queues, but live events quickly catch it up to what is moving through them. Only jobs stuck in a specific queue for extended periods of time, with SLAs defined that need that job, would be impacted. None CA Workload Automation SE Version Copyright (C) 2016 CA. All rights reserved. R00841-AL2113-SP1 DESC(CA-7 SERVER FOR IDASH LISTJOBSTATUS DATA INCORRECT). FMID (CAL2B31) PRE ( RO87253 ) SUP ( TR89819 )

9 CA Workload Automation CA 7 Edtion CA RS PTF RO RO89941 RO89941 M.C.S. ENTRIES = ++PTF (RO89941) XPJOBS NOT TRACKING WITH XPHAO OPTION XPJOBs that use the XPHAO parameter fail to track. XPJOBs stay stuck in the RDY queue. XPJOBs are not tracking in CA 7. Remove the XPHAO option from the XPDEF statement and recycle CA Copyright (C) 2016 CA. All rights reserved. R00843-AL2113-SP1 DESC(XPJOBS NOT TRACKING WITH XPHAO OPTION). FMID (CAL2B30) PRE ( RO18966 RO87801 ) SUP ( AR87801 TR89941 )

10 CA Workload Automation CA 7 Edtion CA RS PTF RO RO90123 RO90123 M.C.S. ENTRIES = ++PTF (RO90123) SASSHE06 - HISTORY 6 REPORT AND JOB COMP CODE If a program does not set a valid return code (the valid range is ), then it is possible that the history 06 report may show a job condition code value that is different than the highest step condition code value. This change will have the job condition code value consistent with the step condition code value, even though neither is valid. History 06 report differences. Low. None. PRODUCTS AFFECTED: CA 7 r11.3 CA Workload Automation SE Version Copyright (C) 2016 CA. All rights reserved. R00845-AL2113-SP1 DESC(SASSHE06 - HISTORY 6 REPORT AND JOB COMP CODE). FMID (CAL2B30) SUP ( TR90123 )