Loading an Event definition into ESP fails with "ESP101W INVALID COMMAND"

Products

• ESP Workload Automation

Issue/Introduction

You use JCL to transfer events between ESP systems. If a line exceeds 72 character limits, ESP puts the dash as the 73rd character and the transfer process fails.

Here is an example of Event definition with lines over 72 chars:

EVENT ID(CYBER.MYEVENT)  SYSTEM(-)  
REPLACEINVOKE 'CYBER.PROCLIB(EVENT1)'WOBTRIG FILE_TRIGGER Agent(MYAGENT) - 
FileName('/this/is/my/filename/path/where/the/file/is/located.txt') - 
CREATE NoChange(1) State(Working)ENDDEF

Environment

Component: WORKLOAD AUTOMATION ESP 
Release:  All

Resolution

Historically, positions 73 - 80 were used to store user IDs, numbers, etc., so ESP ignores any text beyond this position. This applies only for datasets which are allocated with FB record format and length of 80 characters.

To prevent this behavior, allocate the dataset for event export with a different length such as 133.

Sample JCL to export events to a data set: 

//ESPJLOAD JOB ,ESPJLOAD,MSGLEVEL=(1,1),MSGCLASS=X,REGION=4M
//*=====================================================================
//***  EVENT DOWNLOAD PROCESS  FROM ONE LPAR                                                
//*=====================================================================
//LOADEVNT EXEC PGM=ESP,PARM='SUBSYS(ESPx)',COND=(0,NE)
//STEPLIB  DD   DISP=SHR,DSN=your.ESP.load.library
//SYSPRINT DD   SYSOUT=*
//SYSIN    DD   * 
LIST LEVEL(cyber.myevent) ALL PRINT('hlq.lrecl133.dataset.name')
/*