search cancel

V21 - Forced memory trace with z/OS JOBF - JPEXEC_R Cannot load conversation memory

book

Article ID: 243510

calendar_today

Updated On:

Products

CA Automic One Automation

Issue/Introduction

On a system with 21.0 z/OS agents connecting to a TLS Gateway and filetransfers running, the system forces a trace.  This tends to happen more on systems with 12.3 systems conencted.

The following shows up in the WP logs:

System is running and then will force traces with:
06 - 20220415/075045.056 - U00003422 WARNING: Cannot load conversation memory '1fffa376' for server routine 'JPEXEC_R'.
06 - 20220415/075045.056 - U00009907 Memory dump 'Input memory' (Address='000001C430401010', Length='304')
06 - 20220415/075045.056 -           00000000  51554954 54202020 30310100 0CAD1600  >QUITT   01...­..<
06 - 20220415/075045.056 -           00000010  4E4B0000 46545853 454E4420 00000000  >NK..FTXSEND ....<
06 - 20220415/075045.056 -           00000020  00000000 912C0000 31373033 35383638  >....‘,..17035868<
06 - 20220415/075045.056 -           00000030  36202020 20202020 20202020 20202020  >6               <
06 - 20220415/075045.056 -           00000040= 20202020 20202020 20202020 20202020  >                <
06 - 20220415/075045.056 -           00000120  20202020 20202020 00000000 00000000  >        ........<
06 - 20220415/075045.072 - U00011801 Error in Server routine 'JPEXEC_R', Server: 'UC4T#WP003' AE system: 'UC4T'.
06 - 20220415/075045.072 - U00003422 WARNING: Cannot load conversation memory '1fffa376' for server routine 'JPEXEC_R'.
02 - 20220415/075045.322 - U00015006 System forced memory trace dump.
02 - 20220415/075045.322 - U00015006 System forced memory trace dump.
02 - 20220415/075045.322 - U00003631 Dump caused by:
02 - 20220415/075045.322 - U00003422 WARNING: Cannot load conversation memory '1fffa376' for server routine 'JPEXEC_R'.
02 - 20220415/075045.322 - U00011801 Error in Server routine 'JPEXEC_R', Server: 'UC4T#WP003' AE system: 'UC4T'.

Environment

Release : 21.0, prior to 21.0.4

Cause

This is caused by a bug with the z/OS agent where z/OS agent transfer file to partner via TLS gateway and the TLS GW was sent to QUIT signals.  Since the first one actually stops what needs to be stopped, the second causes a trace since the system does not know how to handle it.

Resolution

Resolved with the z/OS agent release 21.0.4

Description: z/OS Agent File Transfer forces memory dump in Automation Engine Working process in 'JPEXEC_R' module