CA Workload Automation ESP Edition 11.4 1 CA RS … Workload Automation ESP Edition 11.4 1 ......

CA Workload Automation ESP Edition 11.4 1

CA RS 1309 Service ListCA Workload Automation ESP Edition 11.4 1

CA RS 1309 Service List

Release Service Description Hiper

11.4 RO56050 IRRNNNI MESSAGES CAUSING INCORRECT JCLERROR STATUS

RO56572 ESP MASTER CHECKPOINT MAY FILL UP DURING STARTUP

RO56585 CONSOLE TRACKING DADSM OBTAIN

RO56797 ABEND S0C4 IN CYBRM013

RO56897 NOTIFY INDICATES ENDED INSTEAD OF FAILED

RO56916 EXTERNAL OF SELFCOMPL TASK IS POSTED WHEN FORCED COMPLETE

RO56977 INADVERTENT ESP JOB RESTARTS

RO57146 ABEND U2999 IN MAPGEN JOB

RO57215 INCORRECT BATCH SIMULATE NORUN RC 0

RO57226 LOW BATCH RC AFTER AN ERROR IN SADGEN

RO57234 BYPASSED EXTMON OBJECT NOT RELEASING SUCCESSORS

RO57345 ERROR MESSAGES BROWSING JCL FROM WORKSTATION

RO57413 WORKSTATION SERVER U1013

RO57479 ABEND SD23 ON SEND COMMAND

RO57516 ENABLE FILTERING BY TAG AND SUBAPPL IN LSAR

RO57523 CSF SHOWS A WRONG RETURN CODE FOR ABENDED JOB

RO57528 EXTERNAL DETAILS INFORMATION

RO57530 APPLS IN REXXON EXEC STATUS

RO57584 INSERTING JOB AFTER APPLEND CAUSES LOOP

RO57604 TEST SYSTEM PROXY TASK ABEND

RO57641 ABEND S0C4 IN TRACEPRT COMMAND

RO57689 UNPOPULATED MNSYS VARIABLE

RO57700 CA LICENSING SMF PRODUCT INFORMATION

RO57764 LONG COND STATEMENTS TRUNCATED

RO58092 SUPPORT ESP IN MULTI-TASKING TSO ENVIRONMENT

RO58148 MONITORING FOR MANUAL JOBS WITH JCL ERRORS

RO58196 VSAM RECORD LENGTH DISCREPANCY WITH INTERNAL RECORD LENGTH

RO58198 JOB INDEX FILE SYNCHRONIZATION

RO58290 HEALTHCK COMMAND COMPATIBILITY

RO58385 INTERNAL OPER COMMAND HANG WAITING FOR DSPMODE TASKS COMMAND

RO58422 ESP MASTER ABENDS WITH U1013, S0C4, S0C6

RO58436 APPLICATION CAN STAY IN APPLWAIT AFTER ESP4174W

RO58511 ABEND S0C4 IN WKSTART AND WORKDAY COMMANDS

RO58621 APPLICATION SCOREBOARD PURGE PROBLEM

RO58765 JOB WITH INVERSE RESOURCE REQUEST MAY STAY IN RESWAIT

RO58796 CHECKING FOR SPURIOUS ENDDOS

RO59082 S0C4 ABEND IN FAILOVER MANAGER

RO59147 SELECTION OF HIGH COMPLETION CODE DISREGARDS CCCHK

RO59158 LOCAL JOB JCL ERROR NOT DETECTED

RO59247 MESSAGE 1062I DESCRIPTION ADDED

RO59300 S122 IF SUBSYSTEM STARTED DURING LMP INITIALIZATION

RO59301 ABEND S0C4 DUE TO SYMBOLIC VARIABLE SUBSTRING

RO59306 WRONG COND STATEMENT USED WHEN RESET THROUGH MGRMSG

RO59341 APPLICATION SLOT OVERLAYS NOT DETECTED BY CYBESUT1

RO59353 ESP609E PARAMETER NOT VALID

RO59627 LEAK OF SEND COMMAND RESPONSE ELEMENTS

RO59689 PLATFORM-SPECIFIC PASSWORDS FOR PROXY_JOB

RO59759 EAV COMPATIBILITY WITH ESP

RO59791 MANUAL TRIGJOB NOT POSTED WHEN JCL ERROR

The CA RS 1309 service count for this release is 49


CA RS 1309 Service ListCA Workload Automation ESP Edition 11.3 2

CA RS 1309 Service List

Release Service Description Hiper

11.3 RO57013 Bypassed EXTMON WOB not releasing successors


RO57015 The Application Monitor displays invalid value in the

RO57139 ESPWSS906E INVLD KWRD ERROR MSG ON ATTEMPT TO BROWSE JCL

RO57258 Workstation started task abended on a U1013


RO57381 SD23 ABEND ON SEND COMMAND

RO57392 TRACEPRT COMMAND CAN CAUSE S0C4


RO57505 MULTIPLE AJ INSERTS RESULT IN 0C4 ABEND

RO57506 ESP MASTER ABENDS WITH U1013, S0C4, S0C6.




RO58461 CA Licensing Product SMF Information

RO58571 Application scoreboard purge bug

RO58647 Checking for spurious ENDDOs

RO58807 S0C4 abend in Failover Manager

RO58939 Application slot overlays not detected by CYBESUT1

RO58940 Incorrect dynamic allocation failure message

RO58997 Manual TRIGJOB not posted when JCL error

RO58998 TDRs for STEPEND monitor events may fill up ESP checkpoint


RO59249 LLMP command response License field misalignment

RO59486 "Unable to find password" message issued incorrectly

RO59487 Platform-specific passwords for PROXY_JOB



RO60322 NEW MSG FOR LOADAGDF WITH TEST

The CA RS 1309 service count for this release is 29

CA Workload Automation ESP Edition 3

CA RS 1309 Service List for CD7YB30CA Workload Automation ESP Edition 3

CA RS 1309 Service List for CD7YB30

FMID Service Description Hiper

CD7YB30 RO57013 Bypassed EXTMON WOB not releasing successors


RO57015 The Application Monitor displays invalid value in the

RO57139 ESPWSS906E INVLD KWRD ERROR MSG ON ATTEMPT TO BROWSE JCL


RO57381 SD23 ABEND ON SEND COMMAND


RO57505 MULTIPLE AJ INSERTS RESULT IN 0C4 ABEND

RO57506 ESP MASTER ABENDS WITH U1013, S0C4, S0C6.


RO58571 Application scoreboard purge bug

RO58807 S0C4 abend in Failover Manager

RO58939 Application slot overlays not detected by CYBESUT1

RO58997 Manual TRIGJOB not posted when JCL error

RO58998 TDRs for STEPEND monitor events may fill up ESP checkpoint


RO59486 "Unable to find password" message issued incorrectly

RO59487 Platform-specific passwords for PROXY_JOB


RO60322 NEW MSG FOR LOADAGDF WITH TEST

The CA RS 1309 service count for this FMID is 20


CA RS 1309 Service List for CD7YB40CA Workload Automation ESP Edition 4

CA RS 1309 Service List for CD7YB40


CD7YB40 RO56050 IRRNNNI MESSAGES CAUSING INCORRECT JCLERROR STATUS

RO56572 ESP MASTER CHECKPOINT MAY FILL UP DURING STARTUP

RO56585 CONSOLE TRACKING DADSM OBTAIN

RO56797 ABEND S0C4 IN CYBRM013

RO56897 NOTIFY INDICATES ENDED INSTEAD OF FAILED

RO56916 EXTERNAL OF SELFCOMPL TASK IS POSTED WHEN FORCED COMPLETE

RO56977 INADVERTENT ESP JOB RESTARTS

RO57146 ABEND U2999 IN MAPGEN JOB

RO57215 INCORRECT BATCH SIMULATE NORUN RC 0

RO57226 LOW BATCH RC AFTER AN ERROR IN SADGEN

RO57234 BYPASSED EXTMON OBJECT NOT RELEASING SUCCESSORS

RO57345 ERROR MESSAGES BROWSING JCL FROM WORKSTATION

RO57413 WORKSTATION SERVER U1013

RO57479 ABEND SD23 ON SEND COMMAND

RO57516 ENABLE FILTERING BY TAG AND SUBAPPL IN LSAR

RO57523 CSF SHOWS A WRONG RETURN CODE FOR ABENDED JOB


RO57530 APPLS IN REXXON EXEC STATUS


RO57604 TEST SYSTEM PROXY TASK ABEND

RO57641 ABEND S0C4 IN TRACEPRT COMMAND

RO57689 UNPOPULATED MNSYS VARIABLE

RO57700 CA LICENSING SMF PRODUCT INFORMATION



RO58148 MONITORING FOR MANUAL JOBS WITH JCL ERRORS


RO58198 JOB INDEX FILE SYNCHRONIZATION

RO58290 HEALTHCK COMMAND COMPATIBILITY

RO58385 INTERNAL OPER COMMAND HANG WAITING FOR DSPMODE TASKS COMMAND

RO58422 ESP MASTER ABENDS WITH U1013, S0C4, S0C6


RO58511 ABEND S0C4 IN WKSTART AND WORKDAY COMMANDS

RO58621 APPLICATION SCOREBOARD PURGE PROBLEM


RO58796 CHECKING FOR SPURIOUS ENDDOS

RO59082 S0C4 ABEND IN FAILOVER MANAGER

RO59147 SELECTION OF HIGH COMPLETION CODE DISREGARDS CCCHK

RO59158 LOCAL JOB JCL ERROR NOT DETECTED

RO59247 MESSAGE 1062I DESCRIPTION ADDED

RO59300 S122 IF SUBSYSTEM STARTED DURING LMP INITIALIZATION

RO59301 ABEND S0C4 DUE TO SYMBOLIC VARIABLE SUBSTRING


RO59341 APPLICATION SLOT OVERLAYS NOT DETECTED BY CYBESUT1


RO59627 LEAK OF SEND COMMAND RESPONSE ELEMENTS

RO59689 PLATFORM-SPECIFIC PASSWORDS FOR PROXY_JOB

RO59759 EAV COMPATIBILITY WITH ESP

RO59791 MANUAL TRIGJOB NOT POSTED WHEN JCL ERROR



CA RS 1309 Service List for CD9EB30CA Workload Automation ESP Edition 5

CA RS 1309 Service List for CD9EB30


CD9EB30 RO57258 Workstation started task abended on a U1013

RO57392 TRACEPRT COMMAND CAN CAUSE S0C4



RO58461 CA Licensing Product SMF Information

RO58647 Checking for spurious ENDDOs

RO58940 Incorrect dynamic allocation failure message

RO59249 LLMP command response License field misalignment




CA RS 1309 - PTF RO56050 DetailsCA Workload Automation ESP Edition 11.4 6

CA RS 1309 - PTF RO56050 Details

Release Service Details11.4 RO56050 RO56050 M.C.S. ENTRIES = ++PTF (RO56050)

IRRNNNI MESSAGES CAUSING INCORRECT JCLERROR STATUS

PROBLEM DESCRIPTION:

Security message IRRnnnI that contains keywords

VERIFICATION FAILED can mark a job completed

with JCLERROR status, even if the job has already

started and is running.

This fix makes ESP ignore IRRnnn messages for

such jobs.

SYMPTOMS:

After receiving IRRnnnI message, ESP marks a job

as complete with the JCLERROR status.

At the same time, the real job is up and running.

IMPACT:

The job is incorrectly completed by ESP and the

JCLERROR status is set to it.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA Workload Automation ESP Edition r11.4

Star Problem(s):

ESPWA 1364

Copyright (C) 2013 CA. All rights reserved. R00317-D7Y114-SP1

DESC(IRRNNNI MESSAGES CAUSING INCORRECT JCLERROR STATUS) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO55795 )

SUP ( RO54904 TR54904 TR55951 TR56050 )





ESP MASTER CHECKPOINT MAY FILL UP DURING STARTUP


There could be a situation when the master checkpoint data

set is filled up by tracking records from the proxies if

the proxies are started before the master. It may cause a

deadlock between the application and tracking managers

when the application manager needs to wait for checkpoint

space while the tracking manager waits for the application

manager to complete its initialization.

SYMPTOMS:

Messages indicating that the checkpoint file is full.

No events, jobs, applications are processed by ESP.

IMPACT:

ESP outage.

CIRCUMVENTION:

ESP cold start.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1343


DESC(ESP MASTER CHECKPOINT MAY FILL UP DURING STARTUP) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR56572 )





CONSOLE TRACKING DADSM OBTAIN


The IBM Console Tracking Facility reports a potential DADSM

OBTAIN error by Encore program CYBRM000. The error will occur if

the Encore EXH data set is EAS-eligible and the z/OS release is

V1.R12 or later. This fix implements proper EAV (Extended Address

Volume) support for the Encore EXH data set.

SYMPTOMS:

The following error message is issued by the Console Tracking Facility:

---TRACKING INFORMATION---- -VALUE-- JOBNAME PROGNAME+OFF-- ASID NUM

SMS-E:1 DADSM OBTAIN C10001 DXYWMAWA CYBRM000 20802 91 1

IMPACT:

The Encore EXH data set will be unusable if it resides on an EAV

(Extended Address Volume) and the z/OS release is V1.R12 or later.

CIRCUMVENTION:

None.

PRODUCT(S) AFFECTED:

CA Workload Automation Restart Option ESP Edition Release 11.4

Star Problem(s):

ESPWA 1378


DESC(CONSOLE TRACKING DADSM OBTAIN) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO49741 )

SUP ( TR56585 )





ABEND S0C4 IN CYBRM013


Sometimes Encore allocates a bigger buffer

for processing a job execution history request.

Occasionally, not all pointers are

updated with the new buffer address and this can lead

to a S0C4 abend. This fix ensures that all pointers

are correctly updated after the new buffer is

allocated.

SYMPTOMS:

ESP abends with S0C4 abend in the load module CYBRM011.

The title of the SVC dump reports "subtask ABEND0C4 in CYBRM013".

IMPACT:

S0C4 abend.

CIRCUMVENTION:

None.



Star Problem(s):

ESPWA 1380


DESC(ABEND S0C4 IN CYBRM013) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO49741 RO55479 )

SUP ( TR56797 )





NOTIFY INDICATES ENDED INSTEAD OF FAILED


Notifications sent due to NOTIFY FAILURE contain the word ENDED

rather than FAILED.

SYMPTOMS:

For the jobs that abended, failed with CCCHK or JCL error, the

notification would indicate that the job ENDED.

IMPACT:

None.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1369


DESC(NOTIFY INDICATES ENDED INSTEAD OF FAILED) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )

SUP ( RO54904 TR54904 TR55951 TR56897 )





EXTERNAL OF SELFCOMPL TASK IS POSTED WHEN FORCED COMPLETE


When USERMOD 30 is on, the external of SELFCOMPLETING TASK will be

posted if the TASK is forced complete. New USERMOD 91 has been introduced

to disable posting externals of the SELFCOMPLETING TASK.

SYMPTOMS:

External of the SELFCOMPLETING TASK is posted complete when the home

job is forced complete.

IMPACT:

The user cannot force complete the application without posting

externals.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1375


DESC(EXTERNAL OF SELFCOMPL TASK IS POSTED WHEN FORCED COMPLETE) .

++VER (Z038)

FMID (CD7YB40)

SUP ( RO48789 RO51846 RO52128 RO52192 RO56370 TR48789

TR51846 TR51949 TR52128 TR52192 TR53881 TR54135

TR56370 TR56417 TR56916 )





INADVERTENT ESP JOB RESTARTS


When a job with JOBID=0 is selected in CSF for resubmission, Encore

restart panel CYBESS10 incorrectly offers to restart the job (by filling

the field 'Restart ===> Y' in the CYBESS10 panel).

After applying the fix the Encore restart panel will correctly offer to

resubmit the job (by filling the field 'Restart ===> N' in the CYBESS10

panel).

SYMPTOMS:

The Encore restart panel CYBESS10 incorrectly offers to restart the job

instead of to resubmit it, if JOBID=0.

IMPACT:

The Encore restart panel offers the user to restart a job instead of to

resubmit it.

CIRCUMVENTION:

Change the 'Restart ===> Y' option field in the Encore restart panel

CYBESS10 to 'Restart ===> N'.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1381


DESC(INADVERTENT ESP JOB RESTARTS) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50380 RO55270 )

SUP ( RO54132 RO54217 TR52533 TR54110 TR54132 TR54217

TR56814 TR56977 )





ABEND U2999 IN MAPGEN JOB


This abend occurs in the MAPGEN job if the length

of the parameter list on the RUN/NORUN statement

exceeds 4080 characters.

SYMPTOMS:

MAPGEN job ends with ABEND U2999.

IMPACT:

Inability to use JOBMAP and JOBTREE commands.

CIRCUMVENTION:

Code multiple RUN/NORUN statements instead of one.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1367


DESC(ABEND U2999 IN MAPGEN JOB) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO56359 )

SUP ( RO51917 TR51917 TR56317 TR56481 TR57041 TR57050

TR57052 TR57053 TR57146 )





INCORRECT BATCH SIMULATE NORUN RC 0


When the SIMULATE command is used in a batch job and the simulated

workload object contains a NORUN statement with invalid schedule

criteria, the batch job wrongly completes with return code zero.

SYMPTOMS:

The batch job completes with return code zero even when the workload

object simulation includes an error in a NORUN statement.

IMPACT:

A user is not notified when the SIMULATE command contains errors.

CIRCUMVENTION:

Each batch job output needs to be checked to verify whether the

simulation completed successfully.

PRODUCTS AFFECTED:

CA Workload Automation ESP Edition 11.4

Star Problem(s):

ESPWA 1376


DESC(INCORRECT BATCH SIMULATE NORUN RC 0) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO56359 RO57146 )

SUP ( RO51917 TR51917 TR56481 TR57052 TR57215 )





LOW BATCH RC AFTER AN ERROR IN SADGEN


Errors encountered during simulation of events in SADGEN processing

are not reflected in the condition code of the SADGEN batch job.

This fix uses a recently introduced operator command, BATCHRC

MAXSEV|LEGACY. SADGEN batch jobs will now return a non-zero

condition code in cases where there were WARNING/ERROR/SEVERE

messages during processing. To exploit this feature, the BATCHRC

MAXSEV initialization paramenter has to be coded in the

initialization parameter library used for the SADGEN batch job run.

SYMPTOMS:

SADGEN ends with RC=0 even when there are errors in the execution.

IMPACT:

The SADGEN processing might be wrongly considered as successful.

CIRCUMVENTION:

Check the SYSPRINT output of SADGEN job for any errors.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1385


DESC(LOW BATCH RC AFTER AN ERROR IN SADGEN) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO54033 RO57146 )

SUP ( TR57053 TR57226 )





BYPASSED EXTMON OBJECT NOT RELEASING SUCCESSORS


When a job monitored by the EXTMON workload object in an ESP

application is bypassed by a remote user, the status of the EXTMON

workload object is correctly changed to BYPASSED, but successors are

not released. This fix ensures that all successor workload objects

are properly released after the EXTMON workload object is bypassed.

SYMPTOMS:

CSF shows status BYPASSED for a bypassed EXTMON workload object,

but successors still have non-zero hold counts and

will not run.

IMPACT:

Workload is not processed as expected

CIRCUMVENTION:

N/A

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1388


DESC(BYPASSED EXTMON OBJECT NOT RELEASING SUCCESSORS) .

++VER (Z038)

FMID (CD7YB40)

SUP ( RO48789 RO51846 RO52128 RO52192 RO56370 RO56916

TR48789 TR51846 TR51949 TR52128 TR52192 TR53881

TR54135 TR56370 TR56417 TR56916 TR57234 )





ERROR MESSAGES BROWSING JCL FROM WORKSTATION


When attempting to browse, from Workstation, the JCL of a job with

the same name as a DSTRIG object with a qualifier, in the same

application, multiple "906E INVALID KEYWORD" error messages are

displayed.

SYMPTOMS:

Multiple "906E INVALID KEYWORD" error messages are displayed when trying

to browse a job's JCL from Workstation.

IMPACT:

User cannot browse the JCL of a job from Workstation.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA ESP Workload Automation ESP Edition r11.4

Star Problem(s):

ESPWA 1392


DESC(ERROR MESSAGES BROWSING JCL FROM WORKSTATION) .

++VER (Z038)

FMID (CD7YB40)

SUP ( RO55156 TR45665 TR54997 TR55156 TR57345 )





WORKSTATION SERVER U1013


Workstation Server abended U1013 during logoff processing of a

Workstation user.

SYMPTOMS:

Workstation Server abend U1013

IMPACT:

Restart required.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1395


DESC(WORKSTATION SERVER U1013) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR57413 )





ABEND SD23 ON SEND COMMAND


An abend SD23 can occur when a SEND command is issued with text length

equal to 124 characters.

SYMPTOMS:

ESP master abend SD23.

IMPACT:

ESP master outage.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1396


DESC(ABEND SD23 ON SEND COMMAND) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50049 RO56359 )

SUP ( TR57479 )





ENABLE FILTERING BY TAG AND SUBAPPL IN LSAR


The LSAR command will accept two new optional parameters, TAG and

SUBAPPL:

TAG{(tag1 {tag2} ...)}

SUBAPPL{(subappl1 {subappl2} ...)}

The values of tag1, tag2, ... and subappl1, subappl2, ... are used to

restrict the LSAR report to records with matching tags and/or subappl

fields. Wildcard characters, hyphen and asterisk, are accepted.An

empty value or a value containing a delimiter must be enclosed in

quotes:

SUBAPPL('')

TAG('MONTHLY JOBS')

Filtering by TAG/SUBAPPL is available in all types of LSAR reports.

When TAG and/or SUBAPPL is coded in an LSAR command for a regular or a

PROJECTED report, the corresponding column is added to the report

output. Specifying TAG/SUBAPPL without values adds the attribute to the

ouput without additional filtering.

The FORECASTING ACTIVITY dialog (option S from the main entry panel)

will also accept the new parameters.

SYMPTOMS:

N/A.

IMPACT:

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:

CA Workload Automation ESP Edition 11.4

Star Problem(s):

ESPWA 1384


DESC(ENABLE FILTERING BY TAG AND SUBAPPL IN LSAR) .

++VER (Z038)

FMID (CD7YB40)

SUP ( RO48787 TR48787 TR57217 TR57516 )





CSF SHOWS A WRONG RETURN CODE FOR ABENDED JOB


During initialization of a job, the JES initiator could not obtain a

region required to run the step and a system 822 abend is received.

However, CSF will show the highest return code from the previous steps

or RC=0 for a single step job.

SYMPTOMS:

A job abended with S822 but ESP reports the highest return code from the

previous steps or RC=0 for a single step job.

IMPACT:

Wrong RC is used.

MN variables don't show the correct values.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1371


DESC(CSF SHOWS A WRONG RETURN CODE FOR ABENDED JOB) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )


TR56918 TR57523 )





EXTERNAL DETAILS INFORMATION


ESP does not properly propagate the start and end

times of the home job to the externals with

SCHEDULED or SCOPE set. This causes CA Workload

Automation Workstation to display the current time

instead. After applying the fix, CA Workload

Automation Workstation displays the correct times

for the externals with SCHEDULED or SCOPE set.

SYMPTOMS:

CA Workload Automation Workstation shows wrong start and end times

for the externals with SCHEDULED or SCOPE parameter set.

IMPACT:

Confusion when the external has been completed.

CIRCUMVENTION:

NONE

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1389


DESC(EXTERNAL DETAILS INFORMATION) .

++VER (Z038)

FMID (CD7YB40)


RO57234 TR48789 TR51846 TR51949 TR52128 TR52192

TR53881 TR54135 TR56370 TR56417 TR56916 TR57234

TR57240 TR57528 )





APPLS IN REXXON EXEC STATUS


The Application Monitor displays an invalid value in the

Status_Details field of a complete application, when the last job

in the application is a LINK PROCESS and ESP REXX is executed

for that last LINK job.

SYMPTOMS:

The Application Monitor Status_Details field of a complete application

shows on the master: 'Ended at ' ,

where blanks are displayad instead of the completion time.

shows on the proxy: 'Ended at 16:29 NOV15',

when the proxy is missing the

notification about the last link REXX execution,

or 'REXXON EXEC=20m10s',

when the proxy was notified

about the last link REXX start, but not notified about

its end.

The number of REXXON calls, displayed by the LAE commands,

is different on the master and proxies.

IMPACT:

Incorrect message displayed in the ApplMon Status_Details field.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1387


DESC(APPLS IN REXXON EXEC STATUS) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO55270 RO56359 RO57146 )


RO56370 RO56916 RO57215 RO57234 RO57528 TR48789

TR51846 TR51917 TR51949 TR52128 TR52192 TR53420

TR53881 TR54135 TR56370 TR56417 TR56481 TR56916

TR57052 TR57215 TR57234 TR57240 TR57528 TR57530 )





INSERTING JOB AFTER APPLEND CAUSES LOOP


When inserting a job into an application after another job that is a

successor of APPLEND, the inserted job becomes a predecessor of APPLEND

and a loop occurs.

SYMPTOMS:

The jobs stay in PREDWAIT state indefinitely. Messages 6221W and

6222I are displayed.

IMPACT:

The workload couldn't be resumed.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1398


DESC(INSERTING JOB AFTER APPLEND CAUSES LOOP) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR57584 )





TEST SYSTEM PROXY TASK ABEND


When Encore processes the job end request for a job with a large number

of dynamic allocations, exceeding the number of slots available in the

EXH file, it issues the appropriate message (ID 7187), but it

mistakenly escapes the job end signal process. This results in the

memory cleaning mechanism being broken. The EXH record for this kind

of job remains in memory after the job finishes executing, it can

cause 0C4 abend. The EXH record should stay in memory for the job

live time only.

SYMPTOMS:

OC4 abend, or memory dump containing the orphan EXH record.

IMPACT:

OC4 abend, or unpredictable.

CIRCUMVENTION:

None.



Star Problem(s):

ESPWA 1399


DESC(TEST SYSTEM PROXY TASK ABEND) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO49741 )

SUP ( TR57604 )





ABEND S0C4 IN TRACEPRT COMMAND


The TRACEPRT command may cause a S0C4 abend in Workstation Server or

the TSO client if an invalid trace data set is specified.

This fix checks the validity of the trace data set before accessing it.

SYMPTOMS:

Abend S0C4 in Workstation Server or TSO client.

IMPACT:

Workstation Server outage or TSO client crash.

CIRCUMVENTION:

Ensure the TRACEPRT command specifies a valid trace data set.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1397


DESC(ABEND S0C4 IN TRACEPRT COMMAND) .

++VER (Z038)

FMID (CD7YB40)


TR57539 TR57641 )





UNPOPULATED MNSYS VARIABLE


The value of the variable MNSYS is not populated correctly.

This can leed to errors in the monitor routines.

SYMPTOMS:

Incorrect or empty variable MNSYS() is passed to the monitor routine.

Error message ESP528E is issued.

IMPACT:

The monitor routine cannot process wrongly formatted variables.

The error message ESP528E is issued.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1373


DESC(UNPOPULATED MNSYS VARIABLE) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )

SUP ( RO54904 RO56897 RO57523 TR54904 TR55951 TR56897

TR56900 TR56918 TR57523 TR57689 )





CA LICENSING SMF PRODUCT INFORMATION


When a CA licensing check occurs for the ESP base

product and its components, product and version

information will be provided to CA Common Services

to be included in the SMF type 89 record written

when ESP is launched.

The additional information will help to more easily

identify ESP product components in an IBM IFAURP

utility report for all CA products.

SYMPTOMS:

In an IBM IFAURP utility report, ESP version information is missing and

ESP product information is cryptic.

IMPACT:

There may be some difficulty to accurately determine from an IBM IFAURP

utility report which ESP components have been launched.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1346


DESC(CA LICENSING SMF PRODUCT INFORMATION) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO54908 RO55270 )

SUP ( TR55430 TR55614 TR57700 )





LONG COND STATEMENTS TRUNCATED


COND statements are allowed to be longer than 256 characters. ESP

was truncating the statements after 256 characters.

SYMPTOMS:

Jobs left in PREDWAIT state. Unexplained syntax errors.

CSF display may look like:

ApplName Gen# Job Name Job Qual CCode Jobno P Node Job Status

ICTX87PA 10 ICTOK ~0000002 - TASK PREDWAIT WAITING, HC=1

ICTX87PA 10 MORWI08T ~0000001 0 22941 COMPLETE COMPLETED AT 10.05 22

ESP Job log may have entries such as:

ESP027E (STEPRC('G.LX0432',4) OR STEPRC('G.LX0432',0:1)) AND STEPRC('H.LX0432

ESP004E INVALID STATEMENT SYNTAX

IMPACT:

COND statement failure.

CIRCUMVENTION:

None.


CA Workload Automation ESP Edition Release 11.4

Star Problem(s):

ESPWA 1279


DESC(LONG COND STATEMENTS TRUNCATED) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO56359 RO57146 RO57530 )


RO56916 RO57215 RO57234 RO57528 TR48789 TR51846

TR51917 TR51949 TR52128 TR52192 TR52483 TR53881

TR54135 TR56370 TR56417 TR56481 TR56916 TR57052

TR57215 TR57234 TR57240 TR57528 TR57764 )





SUPPORT ESP IN MULTI-TASKING TSO ENVIRONMENT


This fix introduces an internal change to

support module ESP when it is invoked by third

party products that use a multi-tasking TSO

environment.

SYMPTOMS:

Customer reported that BMC's Mainview AutoOperator got into a loop

while running a REXX that invokes ESP.

IMPACT:

Outage.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1405


DESC(SUPPORT ESP IN MULTI-TASKING TSO ENVIRONMENT) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR58092 )





MONITORING FOR MANUAL JOBS WITH JCL ERRORS


When a manual job is tracked by a TRACKDEF definition

that specifies a model where a MONITOR group or

generic monitor events are defined, that manual job

must trigger those monitor events. However, when

there was a JCL error for a manual job, it does not

trigger monitor events. This fix implements processing

of monitor events for manual jobs with JCL errors.

SYMPTOMS:

No expected monitor events are triggered.

IMPACT:

Monitoring not working as designed for manual jobs

with JCL errors.

CIRCUMVENTION:

N/A

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1406


DESC(MONITORING FOR MANUAL JOBS WITH JCL ERRORS) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )

SUP ( RO54904 RO56897 RO57523 RO57689 TR54904 TR55951

TR56897 TR56900 TR56918 TR57523 TR57689 TR58148 )





VSAM RECORD LENGTH DISCREPANCY WITH INTERNAL RECORD LENGTH


ESP can internally use a larger record length than the actual record

length of a VSAM file in some circumstances. This discrepancy can

occur when a VSAM file is REPROed into a new VSAM file with a smaller

LRECL. This situation can lead to VSAM errors and possible loss of

currently used data:

ESP276E VSAM xxxx ERROR CODE nn ON DATA SET yyyy DABRC=08 DABERRCD=6C

This fix ensures that the internally used record length is not larger

than the VSAM LRECL for each VSAM read.

SYMPTOMS:

'ESP276E VSAM xxxx ERROR CODE nn ON DATA SET yyyy' message is issued

with DABRC=08 and DABERRCD=6C. Other diagnostic messages may follow.

A dump will be captured automatically.

IMPACT:

Possible loss of currently processed data.

CIRCUMVENTION:

Recreation of the affected VSAM file or copying an old VSAM file into

a new one with a larger LRECL.



Star Problem(s):

ESPWA 1408


DESC(VSAM RECORD LENGTH DISCREPANCY WITH INTERNAL RECORD LENGTH) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO51836 )


TR55793 TR58196 )





JOB INDEX FILE SYNCHRONIZATION


There is a rare possibility that the job index file

is not properly reserved when records are read for

update. This can lead to potential synchronization

problems. In particular, error message 903E can

issued by ESP as a result of internal checks.

This PTF fixes this problem.

SYMPTOMS:

Early warning is message 903E (ESP stays up).

IMPACT:

Update of some records in job index file may be not

synchronized, which can lead to processing errors.

CIRCUMVENTION:

N/A

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1409


DESC(JOB INDEX FILE SYNCHRONIZATION) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )

SUP ( RO54904 RO56897 RO57523 RO57689 RO58148 TR54904

TR55951 TR56897 TR56900 TR56918 TR57523 TR57689

TR58148 TR58198 )





HEALTHCK COMMAND COMPATIBILITY


The 11.3 version of the HEALTHCK command has operand NAME

referencing the IBM Health Checker STC name. In 11.4 this name

is supplied automatically, so the old operand NAME has

been removed from the HEALTHCK command structure. That causes

an initialization time error when the old version of the

initialization parameter has been used. For example, HEALTHCK

NAME(HCHECK).

The old operand NAME is now allowed in the 11.4 HEALTHCK command

for compatibility with 11.3.

SYMPTOMS:

ESP906E INVALID KEYWORD, NAME(HCHECK)

ESP804W PARAMETER ERROR ON FOLLOWING STATEMENT FROM ESPPARM FILE

ESP803W HEALTHCK NAME(HCHECK)

*050 LZ113802A REENTER ENTIRE STATEMENT, 'CANCEL' OR 'END'

IMPACT:

Initialization interruption.

CIRCUMVENTION:

Reply without NAME operand: R 50,HEALTHCK

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1412


DESC(HEALTHCK COMMAND COMPATIBILITY) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50049 )

SUP ( TR58290 )





INTERNAL OPER COMMAND HANG WAITING FOR DSPMODE TASKS COMMAND


If an OPER command is issued in the subsystem address space at the

same time an OPER DSPMODE TASKS command is being processed, then a

subsystem hang may occur.

SYMPTOMS:

Subsystem hang.

IMPACT:

Subsystem must be cancelled and restarted.

CIRCUMVENTION:

Avoid issuing OPER DSPMODE TASKS command.



Star Problem(s):

ESPWA 1379


DESC(INTERNAL OPER COMMAND HANG WAITING FOR DSPMODE TASKS COMMAND) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO51349 RO54908 RO55270 )

SUP ( RO57700 TR55430 TR55614 TR56800 TR56974 TR57700

TR58385 )





ESP MASTER ABENDS WITH U1013, S0C4, S0C6


The ESP master may abend if the APPLBUF value in the ESP

initialization parameters is below 3,133,432, and the ATR size grows

over the APPLBUF figure.

SYMPTOMS:

ESP master abends.

IMPACT:

ESP outage.

CIRCUMVENTION:

Increase APPLBUF.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1404


DESC(ESP MASTER ABENDS WITH U1013, S0C4, S0C6) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO57530 RO57764 )


RO57234 RO57528 TR48789 TR51846 TR51949 TR52128

TR52192 TR53881 TR54135 TR56370 TR56417 TR56916

TR57234 TR57240 TR57528 TR58081 TR58422 )





APPLICATION CAN STAY IN APPLWAIT AFTER ESP4174W


ESP completes the oldest active application generation unconditionally when

there are too many active generations and a new application generation is

requested, but do not remove the WAIT status. This can lead to a situation

when the whole generation stream stays in APPLWAIT if the application is

defined with WAIT parameter. With this fix, ESP will remove the WAIT when

completes the oldest active generation.

SYMPTOMS:

Applications stay in APPLWAIT even when there is no active application.

IMPACT:

Application is not processing. The oldest generation is lost every time when

a new generation is created.

CIRCUMVENTION:

Applications reaching maximum concurrent active generations can be defined

with a variable application name, for example APPL MYAPPL%ESPSMN.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1416


DESC(APPLICATION CAN STAY IN APPLWAIT AFTER ESP4174W) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO57530 RO57764 )


RO57234 RO57528 RO58422 TR48789 TR51846 TR51949

TR52128 TR52192 TR53881 TR54135 TR56370 TR56417

TR56916 TR57234 TR57240 TR57528 TR58081 TR58422

TR58436 )





ABEND S0C4 IN WKSTART AND WORKDAY COMMANDS


When an invalid operand more than two characters

is specified in the WKSTART or WORKDAYS command, an

abend S0C4 usually occurs. In addition, when an

invalid operand is specified in the WKSTART or

WORKDAYS command and an abend does not occur, the

error message is not routed to the command issuer.

SYMPTOMS:

Abend S0C4.

IMPACT:

Subsystem outage.

CIRCUMVENTION:

Do not issue the WKSTART or WORKDAYS command with an invalid operand.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1419


DESC(ABEND S0C4 IN WKSTART AND WORKDAY COMMANDS) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO54033 RO57226 )

SUP ( TR58511 )





APPLICATION SCOREBOARD PURGE PROBLEM


Purging application scoreboard elements may result

in incorrect scheduling of purge requests for

proxies, resulting later in abend S0C3. This problem is

highly conditional and depends on the exact timing of

other events, making it a relatively rare problem.

However, it is more likely during a proxy startup,

when the entire scoreboard is transferred from

the master to the proxy. This fix corrects this problem.

SYMPTOMS:

ESP is down due to abend S0C3.

IMPACT:

Disruption of ESP processing

CIRCUMVENTION:

N/A

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1421


DESC(APPLICATION SCOREBOARD PURGE PROBLEM) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR58621 )





JOB WITH INVERSE RESOURCE REQUEST MAY STAY IN RESWAIT


Intermittently, a job with inverse resource request

remains in RESWAIT status when the available count is

equal to zero. It happens when this job enters RESFILE

prior to the other jobs that use up the resource.

The following example illustrates this problem:

1. Resource R1 is defined as AVAIL(1) DEPLETABLE

2. The first application has a job with

RESOURCE ADD(^R1)

The job goes into RESWAIT as expected.

3. The second application has the same job with

RESOURCE ADD(1,R1)

This job runs as expected and depletes the resource,

but the job from #2 remains in RESWAIT even though

the available count of R1 is zero.

SYMPTOMS:

A job with inverse resource request remains in RESWAIT even though

the resource's avalable count is zero.

IMPACT:

Inability to use inverse resource requests

CIRCUMVENTION:

Issue OPER RESREFR command to take the job out of RESWAIT.

PRODUCTS AFFECTED:

CA Workload Automation EE r11.3.

CA Workload Automation ESP Edition r11.4.

Star Problem(s):

ESPWA 1420


DESC(JOB WITH INVERSE RESOURCE REQUEST MAY STAY IN RESWAIT) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO48860 )

SUP ( TR48242 TR48841 TR48854 TR58765 )





CHECKING FOR SPURIOUS ENDDOS


This PTF ensures the integrity of DO/ENDDO statements

in ESP procedures. The feature has an effect only

when usermod 190 is on. For each ENDDO coded out of

sequence (without a preceding DO statement),

error message 322E will be issued and the application

will not be generated. However, when usermod 190 is

off the behavior is not changed (out of sequence

ENDDOs are ignored).

Note that usermod 190 also ensures integrity of

JOB/ENDJOB statements.

SYMPTOMS:

ESP ignores spurious ENDDO statements, rather than reporting

a bug (out of sequence ENDDO).

If there is a spurious ENDDO in an application, which is followed by

a DO statement without closing ENDDO, ESP fails to report missing

ENDDO too.

IMPACT:

Applications may not execute as intended

CIRCUMVENTION:

Review applications and change it to make

DO/ENDDO always consistent.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1424


DESC(CHECKING FOR SPURIOUS ENDDOS) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR58796 )





S0C4 ABEND IN FAILOVER MANAGER


Failover Manager uses an incorrect address of a workload object

message with an invalid format while writing it to

a log. It results in S0C4 abend.

SYMPTOMS:

ESP abends with S0C4.

IMPACT:

Workload processing disruptions

CIRCUMVENTION:

N/A

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1426


DESC(S0C4 ABEND IN FAILOVER MANAGER) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR59082 )





SELECTION OF HIGH COMPLETION CODE DISREGARDS CCCHK


A job failed by CCCHK due to a particular return code may not show that code

if a non-failing but higher completion code was produced by another step.

SYMPTOMS:

CSF status for a failed job may display a non-failing completion code.

A job with CCCHK RC(4) FAIL may have the status

FAILED, CC 12, CCFAIL

although code 12 is not causing the failure.

IMPACT:

The status is shown incorrectly.

CIRCUMVENTION:

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1429


DESC(SELECTION OF HIGH COMPLETION CODE DISREGARDS CCCHK) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )


TR54904 TR55951 TR56897 TR56900 TR56918 TR57523

TR57689 TR58148 TR58198 TR59147 )





LOCAL JOB JCL ERROR NOT DETECTED


Occasionally it can happen that a JCL error is

not detected for a locally submitted job.

This fix corrects the processing of tracking

data that comes out of order.

SYMPTOMS:

The status of a locally submitted job is

sometimes not updated even if the job

failed with a JCL error in JES.

IMPACT:

The status of a job is not updated in CSF.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1430


DESC(LOCAL JOB JCL ERROR NOT DETECTED) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )


RO59147 TR54904 TR55951 TR56897 TR56900 TR56918

TR57523 TR57689 TR58148 TR58198 TR59147 TR59158 )





MESSAGE 1062I DESCRIPTION ADDED


The message description added.

----------------

Message: 1062I

P-NODE NOT DEFINED

Explanation:

The DUEOUT command requires specifying a positional parameter P-NODE.

This informational message will be issued in event simulation

if the P-NODE specified in the DUEOUT command is not defined

in the jobindex via the DEFPN command.

System Action:

Simulation terminates with this informational message, if the P-NODE

in the DUEOUT statement has not been defined.

User Response:

Ensure that the P-NODE name specified in the positional parameter

of the DUEOUT command is intended.

----------------



Star Problem(s):

ESPWA 1433


DESC(MESSAGE 1062I DESCRIPTION ADDED) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR59247 )





S122 IF SUBSYSTEM STARTED DURING LMP INITIALIZATION


If a CA Workload Automation ESP Edition subsystem is

started while the CA Resource Initialization Module

CARIMC is initializing the CA License Management

Prorgam, an abend S122 may occur, even though the

subsystem has not been cancelled.

SYMPTOMS:

Subsystem abend S122.

IMPACT:

Possible confusion.

CIRCUMVENTION:

Start subsystems only after CAIRIMC initialization has completed.

PRODUCTS AFFECTED:


S122 WHEN SUBSYSTEM STARTED DURING LMP INITIALIZATION

Star Problem(s):

ESPWA 1400


DESC(S122 IF SUBSYSTEM STARTED DURING LMP INITIALIZATION) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO54908 RO55270 RO58385 )

SUP ( RO57700 TR55430 TR55614 TR57700 TR59300 )





ABEND S0C4 DUE TO SYMBOLIC VARIABLE SUBSTRING


Substring notation for a character symbolic variable

does not work properly when the length of the variable

is more than 256. If the higher substring index is also

more than 256 then the substring is truncated. If the lower

index is more than 256 it results in a S0C4 abend.

This fix removes the 256-length limitation and ensures

correct substring operation without abend.

SYMPTOMS:

ESP is down due to abend S0C4.

ESP TSO session is down if simulating.

IMPACT:

Disruption of ESP processing.

Application cannot be processed.

CIRCUMVENTION:

N/A



Star Problem(s):

ESPWA 1428


DESC(ABEND S0C4 DUE TO SYMBOLIC VARIABLE SUBSTRING) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR59301 )





WRONG COND STATEMENT USED WHEN RESET THROUGH MGRMSG


ESP uses the incorrect COND statement string when it is RESET

by the MGRMSG command. This will cause a job with the reset

COND statement to stay in predecessor wait status, but only for

COND strings longer than 255 characters. This fix ensures that

the correct COND string is used.

SYMPTOMS:

Jobs left in PREDWAIT state. Unexplained syntax errors.

IMPACT:

COND statement failure.

CIRCUMVENTION:

None.


CA Workload Automation EE r11.3


Star Problem(s):

ESPWA 1425


DESC(WRONG COND STATEMENT USED WHEN RESET THROUGH MGRMSG) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO57530 RO57764 )


RO57234 RO57528 RO58422 RO58436 TR48789 TR51846

TR51949 TR52128 TR52192 TR53881 TR54135 TR56370

TR56417 TR56916 TR57234 TR57240 TR57528 TR58081

TR58422 TR58436 TR59306 )





APPLICATION SLOT OVERLAYS NOT DETECTED BY CYBESUT1


Note: This fix addresses 4 problems.

Problem 1

---------

Prior to this fix the file utility batch program CYBESUT1 did not have

the ability to detect application slot overlays.

CYBESUT1 can now detect and correct application slot overlays, including

those that can potentially cause the subsystem to abend, by marking the

affected applications invalid.

To report application slot overlays that can potentially crash the

subsystem, run batch utility CYBESUT1 with JCL such as the following -

//REPORT JOB ...

//CYBESUT1 EXEC PGM=CYBESUT1,

// PARM=('JOBINDEX(CA.ESP.JOBINDEX)',

// 'APPLFILE(CA.ESP.APPLFILE)')

//STEPLIB DD DISP=SHR,DSN=CA.ESP.CD7YLOAD

//SYSPRINT DD SYSOUT=*

This job may be submitted while ESP subsystems using the same JOBINDEX

and APPLFILE data sets are running. If there are any application slot

overlays that may crash the subsystem, a data line such as the following

will be present in the SYSPRINT file one -

*** Warning *** APPL001.2 (slot 3791) slot 4236 overlaid by APPL006.4,

may cause subsystem failure

The application that caused the slot overlay will only be displayed if

this can be determined.

If ANALYZE is specified in the CYBESUT1 PARM above (not necessary), a

number of application slot overlays will almost certainly be detected

and printed in the SYSPRINT file. They will look something like this -

APPL010.1 (slot 246) not in APPLFILE, overlaid by APPL012.2

The application that caused the slot overlay will only be displayed if

this can be determined.

This kind of overlay is benign as the subsystem is able to detect it.

If at least one warning message of a slot overlay that can potentially

crash the subsystem appears in the SYSPRINT file, the JCL for a CYBESUT1

batch utility run to repair this condition should look something like

the following -

//REPAIR JOB ...

//CYBESUT1 EXEC PGM=CYBESUT1,PARM=('REPAIR',

// 'SUBSYSTEM(ESPM)',

// 'JOBINDEX(CA.ESP.JOBINDEX)',


//STEPLIB DD DISP=SHR,DSN=CA.ESP.CD7YLOAD


*** NOTE ***

------------

The SUBSYSTEM parameter specifies an ESP subsystem running on the same

system as utility CYBESUT1. When specified with the REPAIR (or UPDATE)

operand, the JOBINDEX and APPLFILE data sets can safely be updated while

ESP subsystems using these data sets are active, as CYBESUT1 will

serialize with an ENQ on the ESP subsystem RSVLOGIC resource. This will

prevent concurrent updates of the JOBINDEX and/or APPLFILE data sets by

CYBESUT1 and an ESP subsystem.

The above job will mark any application invalid if it has at least one

slot overlay that can potentially crash the subsystem. Then any attempt

to access that application will result in a "not found" condition.

For each application marked invalid, a message such as the following

will appear in the SYSPRINT file -

APPL001.2 (slot 3791) slot overlay, marked invalid

Note that UPDATE can be specified instead of REPAIR in the above

CYBESUT1 run, but it is not necessary. If UPDATE is specified, then all

applications with slot overlays, including those that are benign, will

be marked invalid.



Release Service DetailsProblem 2

---------

Batch utility program CYBESUT1 does not correctly process jobs with a

JES job number higher than 65535 when processing the TRAKFILE. After

applying this fix, utility CYBESUT1 allows correct processing of all

jobs with JES job numbers from 1 to 999999.

Problem 3

---------

If an attempt to allocate a data set for exclusive use fails because the

data set is allocated to another job then message 2724W, indicating a

shared allocation request failure, is incorrectly issued. This fix

ensures that message 2723W, indicating an exclusive allocation request

failure, is issued when this occurs.

Problem 4

---------

The RSVLOGIC OFF command does not turn the RSVLOGIC facility off when it

follows an RSVLOGIC ENQ or RSVLOGIC RESERVE command in the ESPPARM

initialization data set.

SYMPTOMS:

Problem 1

---------

Most application slot overlays are benign because they are detected by

the subsystem. However, occasionally the subsystem fails to detect an

application overlay. When this occurs there is a potential to crash the

subsystem if an attempt is made to access the application's data.

Problem 2

---------

CYBESUT1 issues message "JOB JOBXYZ(65535) NOT ON TRAKFILE" and reclaims

slots in TRAKFILE for each job with a job number higher than 65535,

regardless of whether or not the job has completed.

Problems 3 and 4

----------------

See DESCRIPTION section.

IMPACT:

Problem 1

---------

A subsystem outage may occur if an attempt is made to access an

application whose data has been corrupted by a slot overlay that the

subsystem is unable to detect.

Problem 2

---------

Utility CYBESUT1 does not work for jobs with JES job numbers higher

than 65535.

Problem 3

---------

None.

Problem 4

---------

The RSVLOGIC facility is unintentionally activated.

CIRCUMVENTION:

Problems 1, 2 and 3

-------------------

None.

Problem 4

---------

Only specify one RSVLOGIC command in the ESPPARM initialization data set.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1354


DESC(APPLICATION SLOT OVERLAYS NOT DETECTED BY CYBESUT1) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50453 RO55795 )



Release Service DetailsSUP ( RO49050 RO55089 TR49050 TR55089 TR59200 TR59341 )

++HOLD (RO59341) SYSTEM FMID(CD7YB40)

REASON (DOC ) DATE (13168)

COMMENT (

The slot reclaim utility CYBESUT1 has two new optional

input parameters, REPAIR and SUBSYSTEM(<name).

REPAIR applies only to CYBESUT1 APPLFILE processing, not

TRAKFILE processing. It requests that any application with

overlaid APPLFILE slots that can potentially crash a

subsystem, be marked unusable.

SUBSYSTEM(<name>), where <name> specifies the name of a

subsystem running on the same system as CYBESUT1, causes

CYBESUT1 to use the subsystem's RSVLOGIC settings to

serialize on the JOBINDEX and TRAKFILE or APPLFILE data sets,

so that no subsystem can update the data sets while CYBESUT1

is performing an UPDATE or REPAIR. If SUBSYSTEM(<name>) is

omitted when UPDATE or REPAIR is specified, then CYBESUT1

allocates the data sets with DISP=OLD instead of DISP=SHR.

See "PROBLEM DESCRIPTION" section in this fix for examples.

Note that after this fix is applied, the QUEISCE and

TRACKING NOSTORE commands no longer need to be issued to

subsystems prior to a CYBESUT1 UPDATE (or REPAIR) run.

Code BYPASS(HOLDSYS) on your APPLY/ACCEPT statement to bypass

this hold.

Product: CA ESP Workload Automation Release: 11.4

Publications: Best Practices Guide and Programmer Guide

).





ESP609E PARAMETER NOT VALID


Error message ESP609E is issued if a year is

specified with an ordinal number in the schedule criteria,

for example, 1st day of Feb 2012.

This fix introduces informational message ESP6127I that will be issued

instead of ESP609E :

ESP6127I - year 'xxxx' is not accepted with ordinals

This way, processing will not be stopped on ESP609E and the user will

get the information that a year specified with an ordinal

number is not accepted.

SYMPTOMS:

Error message ESP609E is issued if a year is specified

with an ordinal number.

IMPACT:

Processing of the schedule criteria stops with error message ESP609E.

CIRCUMVENTION:

Delete the year from the schedule criteria.


CA ESP Workload Automation ESP Edition Release 11.4

Star Problem(s):

ESPWA 1440


DESC(ESP609E PARAMETER NOT VALID) .

++VER (Z038)

FMID (CD7YB40)


TR59353 )





LEAK OF SEND COMMAND RESPONSE ELEMENTS


There can be a leak from the Send command response elements during

event processing if the Send command was issued to a TSO user

who is not currently logged in. This can happen if an

event was triggered by issuing the ESP TRIGGER command in REXX

invoked by CA OPS/MVS. The leak from the Send command

response elements can, over time, cause additional overhead in

event processing. For example, on CSF, the job stays in the 'QUEUED FOR

SUBMISSION' state longer. This fix ensures that the command

response elements are not created for the Send command.

SYMPTOMS:

ESP has been up for several months and the ESP JESMSGLG shows that

many Send commands were issued to CA OPS/MVS. There is a delay in

updating the job status in the CSF and the job stays in the 'QUEUED

FOR SUBMISSION' state longer than usual.

IMPACT:

Delay in updating the job status in the CSF.

CIRCUMVENTION:

Restart of ESP.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1444


DESC(LEAK OF SEND COMMAND RESPONSE ELEMENTS) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR59627 )





PLATFORM-SPECIFIC PASSWORDS FOR PROXY_JOB


PROXY_JOB can be used to work with different platforms, such as Unix or

OpenVMS. These platforms may require their own specific passwords, but the

current PROXY_JOB applications cannot be used to create platform-specific

passwords.

An optional application statement PWDNAME has been created to provide

an ability to specify platform-specific passwords: PWDNAME <name>.

The PASSWORD command can then specify this <name> in its NAME(<name>)

keyword.

SYMPTOMS:

No platform-specific passwords can be created for PROXY_JOB ultimate target

destinations.

IMPACT:

No platform-specific passwords can be created for PROXY_JOB ultimate target

destinations.

CIRCUMVENTION:

N/A

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1445


DESC(PLATFORM-SPECIFIC PASSWORDS FOR PROXY_JOB) .

++VER (Z038)

FMID (CD7YB40)

SUP ( TR59689 )





EAV COMPATIBILITY WITH ESP


The IBM Console Tracking Facility reports a potential OPEN error by ESP

programs CYBXI003 and CYBXK000. The error will occur if an ESP

checkpoint and/or slot file resides on an EAV (Extended Address Volume)

and the z/OS release is 1.12 or later. This fix ensures that ESP

checkpoint and slot files will be fully supported when they reside on

EAVs (Extended Address Volumes) and the z/OS release is 1.12 or later.

SYMPTOMS:

The following error messages are issued by the Console Tracking

Facility:

DCB OPEN EAS 113-44 ESP CYBXI003

DCB OPEN EAS 113-44 ESP CYBXK000

If an attempt is made to open an ESP checkpoint or slot file residing on

an EAV (Extended Address Volume) and the z/OS release is 1.12 or later,

then an abend S113-44 will occur and message IEC142I will be issued.

IMPACT:

ESP checkpoint and slot files residing on EAVs (Extended Address Volumes)

will be unusable if the z/OS release is 1.12 or later.

CIRCUMVENTION:

None.

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1434


DESC(EAV COMPATIBILITY WITH ESP) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO54908 )

SUP ( TR59284 TR59759 )





MANUAL TRIGJOB NOT POSTED WHEN JCL ERROR


A manual job with JCL errors can trigger monitor events

at JOBEND and JOBFAIL monitor points. However, when

these events generate an application with a manual TRIGJOB,

it will not be posted for JCL error.

This fix ensures that TRIGJOB is always posted in

this case and CSF shows the correct status of the job

(failed, JCL error).

SYMPTOMS:

TRIGJOB manual job from monitor application shows MANSUB status

in CSF when a manual job has a JCL error.

IMPACT:

Incorrect job status, successors may not be released

CIRCUMVENTION:

N/A

PRODUCTS AFFECTED:


Star Problem(s):

ESPWA 1435


DESC(MANUAL TRIGJOB NOT POSTED WHEN JCL ERROR) .

++VER (Z038)

FMID (CD7YB40)

PRE ( RO50241 RO55377 RO56050 )


RO59147 RO59158 TR54904 TR55951 TR56897 TR56900

TR56918 TR57523 TR57689 TR58148 TR58198 TR59147

TR59158 TR59299 TR59791 )





DESC (Bypassed EXTMON WOB not releasing successors)

/*-------------------------------------------------------------------

PRODUCT: CA ESP Workload Automation

RELEASE: 11.3

DATE: 2 APR 2013

HYPER: NO

STARTRAK PROBLEM PRODUCT NAME: ESPWA PROBLEM NUMBER: 1247

---------------------------------------------------------------------

Bypassed EXTMON WOB not releasing successors

---------------------------------------------------------------------

When a job monitored by the EXTMON workload object

in an ESP application is bypassed by a remote user,

the status of the EXTMON workload object is correctly changed

to BYPASSED, but its successors are not released.

This fix ensures that all successor workload objects are properly

released after the EXTMON workload object is bypassed.

---------------------------------------------------------------------

PROBLEM RESOLUTION:

Apply the following PTF to the system.

Warm restart CA ESP Workload Automation subsystems.

***NOTE*** Retain the printed output for reference.

-------------------------------------------------------------------*/.

++VER (Z038) FMID(CD7YB30)

PRE (RO56029)

SUP (T5HA185).





DESC (EXTERNAL DETAILS INFORMATION)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 2 APR 2013

HYPER: NO


---------------------------------------------------------------------

EXTERNAL DETAILS INFORMATION

---------------------------------------------------------------------

ESP does not properly propagate the start and end

times of the home job to the externals with SCHEDULED

or SCOPE set. This causes CA Workload Automation

Workstation to display the current time instead.

After applying the fix, CA Workload Automation

Workstation displays the correct times for the

externals with SCHEDULED or SCOPE set.

---------------------------------------------------------------------

PROBLEM RESOLUTION:


Warm restart CA Workload Automation EE subsystems.


-------------------------------------------------------------------*/.


PRE (RO57013)

SUP (T5SK062).





DESC (The Application Monitor displays invalid value in the)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 2 APR 2013

HYPER: NO


---------------------------------------------------------------------

Wrong Status_Details value in Application Monitor

---------------------------------------------------------------------

The Application Monitor displays an invalid value in

the Status_Details field of a complete application,

when the last application job is a LINK PROCESS and

ESP REXX is executed for that last LINK job.

---------------------------------------------------------------------

PROBLEM RESOLUTION:



TSO users reenter ESP sessions.


-------------------------------------------------------------------*/.


PRE (RO55845,RO57014,RO54755,RO53402)

SUP (T5HZ037).





DESC (ESPWSS906E INVLD KWRD ERROR MSG ON ATTEMPT TO BROWSE JCL)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 4 APR 2013

HYPER: NO


---------------------------------------------------------------------

ESPWSS906E INVLD KWRD ERROR MSG ON ATTEMPT TO BROWSE JCL

---------------------------------------------------------------------

While browsing in CA Workload Automation Workstation

EE the JCL of a job that has the same name as a

DSTRIG object with a qualifier, multiple ESPWSS906E

error messages are issued.

---------------------------------------------------------------------

PROBLEM RESOLUTION:





-------------------------------------------------------------------*/.


PRE (RO56023)

SUP (T5TX031).





DESC (Workstation started task abended on a U1013)

/*-------------------------------------------------------------------

PRODUCT: CA Workload Automation EE CPE

RELEASE: 11.3

DATE: 8 APR 2013

HYPER: NO

STARTRAK PROBLEM PRODUCT NAME: ESPCPE PROBLEM NUMBER: 217

---------------------------------------------------------------------

Workstation Server STC abended on U1013

---------------------------------------------------------------------

The Workstation Server started task abended on a

U1013. This abend occurred during the logoff process

of a CA Workload Automation EE Workstation user.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.

++VER (Z038) FMID(CD9EB30)

PRE (RO19674)

SUP (T5HA192).





DESC (INSERTING JOB AFTER APPLEND CAUSES LOOP)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 10 APR 2013

HYPER: NO


---------------------------------------------------------------------

INSERTING JOB AFTER APPLEND CAUSES LOOP

---------------------------------------------------------------------

When inserting a job into an application after

another job which is the successor of APPLEND, the

inserted job becomes a predecessor of APPLEND and

the loop occurs.

---------------------------------------------------------------------

PROBLEM RESOLUTION:





-------------------------------------------------------------------*/.


SUP (T5TX035).





DESC (SD23 ABEND ON SEND COMMAND)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 10 APR 2013

HYPER: NO


---------------------------------------------------------------------

SD23 ABEND ON SEND COMMAND

---------------------------------------------------------------------

An abend SD23 can occur when a SEND command is

issued with text length equal to 124 characters.

---------------------------------------------------------------------

PROBLEM RESOLUTION:





-------------------------------------------------------------------*/.


PRE (RO53855)

SUP (T5TX038).





DESC (TRACEPRT COMMAND CAN CAUSE S0C4)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 10 APR 2013

HYPER: NO


---------------------------------------------------------------------

TRACEPRT COMMAND CAN CAUSE S0C4

---------------------------------------------------------------------

The TRACEPRT command can cause a S0C4

abend of the Workstation Server or

in TSO if it is used with an invalid

trace data set. This fix enforces checks

for the validity of the trace data set.

---------------------------------------------------------------------

PROBLEM RESOLUTION:


Warm restart CA Workload Automation EE subsystems

and Workstation server.

TSO users reenter ESP environment.


-------------------------------------------------------------------*/.


PRE (RO51001)

SUP (T5J4102).





DESC (LONG COND STATEMENTS TRUNCATED)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 12 APR 2013

HYPER: NO


---------------------------------------------------------------------

LONG COND STATEMENTS TRUNCATED

---------------------------------------------------------------------

COND statements are allowed to be longer than 256

characters. ESP was truncating the statements after

256 characters.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO57015,RO52529)

SUP (T5J5036).





DESC (MULTIPLE AJ INSERTS RESULT IN 0C4 ABEND)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 12 APR 2013

HYPER: NO


---------------------------------------------------------------------

MULTIPLE AJ INSERTS RESULT IN 0C4 ABEND

---------------------------------------------------------------------

A large number of AJ INSERT statements result in

an 0C4 abend in ESP.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO57503)

SUP (T5SK063).





DESC (ESP MASTER ABENDS WITH U1013, S0C4, S0C6.)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 12 APR 2013

HYPER: NO


---------------------------------------------------------------------

ESP MASTER ABENDS WITH U1013, S0C4, S0C6.

---------------------------------------------------------------------

The ESP master may abend if the APPLBUF value in the

ESP initialization parameters is below 3,133,432, and

the ATR size grows over the APPLBUF figure.

---------------------------------------------------------------------

PROBLEM RESOLUTION:



-------------------------------------------------------------------*/.


PRE (RO57505)

SUP (T5G9114).





DESC (APPLICATION CAN STAY IN APPLWAIT AFTER ESP4174W)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 23 APR 2013

HYPER: NO


---------------------------------------------------------------------

APPLICATION CAN STAY IN APPLWAIT AFTER ESP4174W

---------------------------------------------------------------------

ESP completes the oldest active application

generation unconditionally when there are too many

active generations and a new application generation

is requested, but does not remove the WAIT status.

This can lead to a situation when the whole

generation stream stays in APPLWAIT if the

application is defined with WAIT parameter. With

this fix, ESP will remove the WAIT when it completes

the oldest active generation.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO57506)

SUP (T5J5038).





DESC (VSAM RECORD LENGTH DISCREPANCY WITH INTERNAL RECORD LENGTH)

/*-------------------------------------------------------------------

PRODUCT: CA ESP Workload Automation CPE

RELEASE: 11.3

DATE: 25 APR 2013

HYPER: NO


---------------------------------------------------------------------

VSAM RECORD LENGTH DISCREPANCY WITH INTERNAL RECORD LENGTH

---------------------------------------------------------------------

ESP can internally use a bigger record length than

the actual record length of a VSAM file in some

circumstances. This discrepancy can happen when a

VSAM file is REPROed into a new VSAM file with a

smaller LRECL. This situation can lead to VSAM

errors and possible loss of currently used data:

ESP276E VSAM xxxx ERROR CODE nn ON DATA SET yyyy

DABRC=08 DABERRCD=6C

The fix ensures that the internally used record

length is not bigger than the VSAM LRECL for every

VSAM read.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO55525)

SUP (T5J5039).

++HOLD(T5J5039) FMID(CD9EB30) SYSTEM REASON(DOC)

COMMENT(This fix introduces a new warning message

ESP993W.

Code BYPASS(HOLDSYS) on your APPLY/ACCEPT

statement to bypass this hold.).





DESC (SUPPORT ESP IN MULTI-TASKING TSO ENVIRONMENT)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 25 APR 2013

HYPER: NO


---------------------------------------------------------------------

SUPPORT ESP IN MULTI-TASKING TSO ENVIRONMENT

---------------------------------------------------------------------

This fix introduces an internal change to

support module ESP when it is invoked by third

party products that use a multi-tasking TSO

environment. This is necessary for obtaining an

address of the currently used TSO/E Environment

Control Table (ECT).

---------------------------------------------------------------------

PROBLEM RESOLUTION:



-------------------------------------------------------------------*/.


SUP (T5G9118).





DESC (CA Licensing Product SMF Information)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 7 MAY 2013

HYPER: NO


---------------------------------------------------------------------

CA Licensing Product SMF Information

---------------------------------------------------------------------

When a CA licensing check occurs for the ESP base

product and its components, product and version

information will be provided to CA Common Services

to be included in the SMF type 89 record written

when ESP is launched.

The additional information will help to more easily

identify ESP product components in an IBM IFAURP

utility report for all CA products.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO54754)

SUP (T5HG159).





DESC (Application scoreboard purge bug)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 9 MAY 2013

HYPER: NO


---------------------------------------------------------------------

Application scoreboard purge problem

---------------------------------------------------------------------

Purge of application scoreboard elements may result

in incorrect scheduling of purge requests for

proxies, resulting later in abend S0C3. The problem is

highly conditional and depends on exact timing of

other events, making it a relatively rare problem.

However, it is more likely during a proxy startup,

when the entire scoreboard is transferred from

the master to the proxy.

This fix corrects this problem.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO44562)

SUP (T5HA189).





DESC (Checking for spurious ENDDOs)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 10 MAY 2013

HYPER: NO


---------------------------------------------------------------------

Checking for spurious ENDDOs

---------------------------------------------------------------------

This PTF ensures integrity of DO/ENDDO statements

in ESP procedures. The feature has an effect only

when usermod 190 is on. For each ENDDO coded out of

sequence (without preceding DO statement) there will

be issued 322E error message and application will

not be generated. However, when usermod 190 is off

the behavior is not changed (out of sequence ENDDOs

are ignored).

Note that usermod 190 also ensures integrity of

JOB/ENDJOB statements.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO24092)

SUP (T5HA176).





DESC (S0C4 abend in Failover Manager)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 15 MAY 2013

HYPER: NO


---------------------------------------------------------------------

S0C4 abend in Failover Manager

---------------------------------------------------------------------

The Failover Manager uses an incorrect address for a

workload object message with an invalid format while

writing it to a log. It results in a S0C4 abend.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO45907)

SUP (T5HA181)

REQ (RO44578).





DESC (Application slot overlays not detected by CYBESUT1)

/*-------------------------------------------------------------------

PRODUCT: CA WORKLOAD AUTOMATION EE

RELEASE: 11.3

DATE: 17 MAY 2013

HYPER: NO


---------------------------------------------------------------------

Application slot overlays not detected by CYBESUT1

---------------------------------------------------------------------

Prior to this fix the file utility batch program

CYBESUT1 did not have the ability to detect

application slot overlays.

CYBESUT1 can now detect and correct application

slot overlays, including those that can potentially

cause the subsystem to abend, by marking the

affected applications invalid.

To report application slot overlays that can

potentially crash the subsystem, run the batch

utility CYBESUT1 with JCL such as the following -

//REPORT JOB ...

//CYBESUT1 EXEC PGM=CYBESUT1,

// PARM=('JOBINDEX(CA.ESP.JOBINDEX)',


//STEPLIB DD DISP=SHR,DSN=CA.ESP.SSCPLINK


This job may be submitted while ESP subsystems

using the same JOBINDEX and APPLFILE data sets are

running. If there are any application slot overlays

that may crash the subsystem, a data line such as

the following will be present in the SYSPRINT file

for each one -

*** Warning *** APPL001.2 (slot 3791) slot 4236

overlaid by APPL006.4, may cause subsystem failure

The application that caused the slot overlay will

only be displayed if this can be determined.

If ANALYZE is specified in the CYBESUT1 PARM above

(not necessary), a number of application slot

overlays will almost certainly be detected and

printed in the SYSPRINT file. They will look

something like this -

APPL010.1 (slot 246) not in APPLFILE,

overlaid by APPL012.2

The application that caused the slot overlay will

only be displayed if it can be determined.

This kind of overlay is benign as the subsystem is

able to detect it.

If at least one warning message of a slot overlay

that can potentially crash the subsystem appears in

the SYSPRINT file, the JCL for a CYBESUT1 batch

utility run to repair this condition should look

something like the following -

//REPAIR JOB ...

//CYBESUT1 EXEC PGM=CYBESUT1,PARM=('REPAIR',

// 'SUBSYSTEM(ESPM)',

// 'JOBINDEX(CA.ESP.JOBINDEX)',


//STEPLIB DD DISP=SHR,DSN=CA.ESP.SSCPLINK


*** NOTE ***

------------

The SUBSYSTEM parameter specifies an ESP subsystem

running on the same system as utility CYBESUT1.

When specified with the REPAIR (or UPDATE) operand



Release Service Detailsthe JOBINDEX and APPLFILE data sets can safely be

updated while ESP subsystems using these data sets

are active, as CYBESUT1 will serialize with an ENQ

on the ESP subsystem RSVLOGIC resource. This will

prevent concurrent updates of the JOBINDEX and/or

APPLFILE data sets by CYBESUT1 and an ESP

subsystem.

If the SUBSYSTEM parameter is omitted when REPAIR

(or UPDATE) is specified, then an outage of all

ESP subsystems using the same JOBINDEX and APPLFILE

data sets will be required, as CYBESUT1 will

allocate these data sets with DISP=OLD.

The above job will mark any application invalid if

it has at least one slot overlay that can

potentially crash the subsystem. Then any attempt

to access that application will result in a

"not found" condition.

For each application marked invalid, a message such

as the following will appear in the SYSPRINT file -

APPL001.2 (slot 3791) slot overlay, marked invalid

Note that UPDATE can be specified instead of REPAIR

in the above CYBESUT1 run but it is not necessary.

If UPDATE is specified, then all applications with

slot overlays, including those that are benign,

will be marked invalid.

Batch utility program CYBESUT1 does not correctly

process jobs with a JES job number higher than

65535 when processing the TRAKFILE. After applying

the fix, utility CYBESUT1 allows correctly

processing all jobs with JES job numbers from 1 up

to 999999.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO26726,RO41067,RO48823)

SUP (T5HG155).

++IF FMID(CD9EB30) THEN REQ(T5HG158).





DESC (Incorrect dynamic allocation failure message)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 17 MAY 2013

HYPER: NO



---------------------------------------------------------------------

Incorrect dynamic allocation failure message

---------------------------------------------------------------------

If an attempt to allocate a data set for exclusive

use fails because the data set is allocated to

another job then message 2724W indicating a shared

allocation request failure is incorrectly issued.

This fix will ensure that message 2723W indicating

an exclusive allocation request failure is issued

when this occurs.

The RSVLOGIC OFF command does not turn the RSVLOGIC

facility off when it follows an RSVLOGIC ENQ or

RSVLOGIC RESERVE command in the ESPPARM

initialization data set.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO21012,RO26479,RO42020)

SUP (T5HG158).





DESC (Manual TRIGJOB not posted when JCL error)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 20 MAY 2013

HYPER: NO


---------------------------------------------------------------------

Manual TRIGJOB not posted when JCL error

---------------------------------------------------------------------

Manual job with a JCL error can trigger monitor events

at JOBEND and JOBFAIL monitor points. However, when

these events run an application containing a manual TRIGJOB,

the job will not be posted for JCL error.

This fix ensures that TRIGJOB is always posted in

this case and CSF shows the correct status of the job

(failed, JCL error).

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO58996)

SUP (T5HA188).





DESC (TDRs for STEPEND monitor events may fill up ESP checkpoint)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 20 MAY 2013

HYPER: NO


---------------------------------------------------------------------

TDRs for STEPEND monitor events may fill up ESP checkpoint

---------------------------------------------------------------------

Intermittently, ESP incorrectly calculates a step end

time. This time is stored in the Job Tracking

Record (JTR) and used as a scheduling time in TDRs

for the STEPEND monitor events. If it falls on a

date & time in the future, then such a TDR may stay

on the checkpoint data set for long time. Numerous

TDRs with these erroneous scheduling times may fill

up the checkpoint data set, causing ESP1880E,

ESP1166E, and ESP1157E error messages displayed.

Also, some stepend monitor events may not fire and

appear missing.

---------------------------------------------------------------------

PROBLEM RESOLUTION:



-------------------------------------------------------------------*/.


PRE (RO58997)

SUP (T5G9119).





DESC (JOB WITH INVERSE RESOURCE REQUEST MAY STAY IN RESWAIT)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 22 MAY 2013

HYPER: NO


---------------------------------------------------------------------

JOB WITH INVERSE RESOURCE REQUEST MAY STAY IN RESWAIT

---------------------------------------------------------------------

Intermittently, a job with inverse resource request

remains in RESWAIT status when the available count is

equal to zero. It happens when this job enters RESFILE

prior to the other jobs that use up the resource.

The following example illustrates this problem:

1. Resource R1 is defined as AVAIL(1) DEPLETABLE

2. The first application has a job with

RESOURCE ADD(^R1)

The job goes in RESWAIT as expected.

3. The second application has the same job with

RESOURCE ADD(1,R1)

This job runs as expected and depletes the resource,

but the job from #2 remains in RESWAIT even though

the available count of R1 is zero.

---------------------------------------------------------------------

PROBLEM RESOLUTION:



-------------------------------------------------------------------*/.


PRE (RO50035)

SUP (T5G9121).





DESC (LLMP command response License field misalignment)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 24 MAY 2013

HYPER: NO


---------------------------------------------------------------------

LLMP command response License field misalignment

---------------------------------------------------------------------

The License field in the LLMP command response

data lines is not aligned with the title in the

header line.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO58940)

SUP (T5HG160).





DESC ("Unable to find password" message issued incorrectly)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 31 MAY 2013

HYPER: NO


---------------------------------------------------------------------

"Unable to find password" message issued incorrectly

---------------------------------------------------------------------

If password retrieval uses the NAME search criterion

a correct password may not be found and retrieved.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO51987)

SUP (T5HC044).





DESC (Platform-specific passwords for PROXY_JOB)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 31 MAY 2013

HYPER: NO


---------------------------------------------------------------------

Platform-specific passwords for PROXY_JOB

---------------------------------------------------------------------

PROXY_JOB can be used to work with different platforms,

such as Unix or OpenVMS. These platforms may require

their own specific passwords, but the current PROXY_JOB

applications cannot be used to create platform-specific

passwords.

An optional application statement PWDNAME has been

created to provide an ability to specify

platform-specific passwords:

PWDNAME <name>.

PASSWORD command can then specify this <name>

in its NAME(<name>) keyword.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO40209,RO59486)

SUP (T5HC043).

++HOLD(RO59487) FMID(CD7YB30) SYSTEM REASON(DOC)

COMMENT(This fix introduces one new optional PROXY_JOB

application statement PWDNAME:

PWDNAME <name>, where <name> is 1 to 64 characters,

case-sensitive, and delimiters are not allowed.

It can be used in the NAME keyword of the PASSWORD

command.







DESC (ESP609E PARAMETER NOT VALID)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 4 JUN 2013

HYPER: NO


---------------------------------------------------------------------

ESP609E PARAMETER NOT VALID

---------------------------------------------------------------------

Error message ESP609E is issued if a year is

specified with an ordinal number in the

schedule criteria, for example,

1st day of Feb 2012. This fix introduces

informational message ESP6127I that will be

issued instead of ESP609E :

ESP6127I - year 'xxxx' is not accepted with ordinals

This way, processing will not be stopped on

ESP609E and the user will get the information

that a year specified with an ordinal number is

not accepted.

---------------------------------------------------------------------

PROBLEM RESOLUTION:


Warm restart CA Workload Automation EE subsystems

and Workstation server.

TSO users reenter ESP environment.


-------------------------------------------------------------------*/.


PRE (RO55507)

SUP (T5J4100).

++HOLD(RO59614) FMID(CD9EB30) SYSTEM REASON(DOC)

COMMENT(This fix introduces the new informational

message 6127I.

If you use an ordinal number with a year,

the specified year will be ignored.

For example, if you specify

1st day of Feb 2012, the year 2012 will

be ignored. The part of a schedule term

before the STARTING operand serves as

an algorithm for computing recurring

dates and times, therefore the number

2012 is considered to be out of context.







DESC (WRONG COND STATEMENT USED WHEN RESET THROUGH MGRMSG)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 10 JUN 2013

HYPER: NO


---------------------------------------------------------------------

WRONG COND STATEMENT USED WHEN RESET THROUGH MGRMSG

---------------------------------------------------------------------

ESP uses the incorrect COND statement string when

it is RESET by the MGRMSG command. This will cause

a job with the reset COND statement to stay in

predecessor wait status, but only for COND strings

longer than 255 characters. This fix ensures that

the correct COND string is used.

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


PRE (RO57914)

SUP (T5J5041).





DESC (NEW MSG FOR LOADAGDF WITH TEST)

/*-------------------------------------------------------------------


RELEASE: 11.3

DATE: 25 JUN 2013

HYPER: NO


---------------------------------------------------------------------

NEW MSG FOR LOADAGDF WITH TEST

---------------------------------------------------------------------

Command LOADAGDT with parameter TEST does not

produce a message that confirms that the test

passed correctly.

The fix adds new message "2982I Agent Definition

Table test has correctly processed" to display

the result.

The full description of the message 2982I:

---

Agent Definition Table test has been correctly

processed

Explanation:

In response to a LOADAGDF initialization parameter

or command with parameter TEST, all syntax and

logical checks of the multi-platform agent

definition table have been correctly processed.

System Action:

The data in the multi-platform agent table is

correct.

User Response:

None

---

---------------------------------------------------------------------

PROBLEM RESOLUTION:




-------------------------------------------------------------------*/.


SUP (T5SK064).

++HOLD(T5SK064) FMID(CD7YB30) SYSTEM REASON(DOC)

COMMENT(This fix includes new message CYB2982.

Code BYPASS(HOLDSYS) on your APPLY/ACCEPT statement

to bypass this hold.).

Date post:	04-Apr-2018
Category:	Documents
Upload:	ngothuy
View:	386 times
Download:	5 times

CA Workload Automation ESP Edition 11.4 1 CA RS … Workload Automation ESP Edition 11.4 1 ......

Documents