CA7 hung. Cannot login. Error REQSESS FAILED - RTNCD=X'10'(016) FDBK2=X'12'(018) SENSE=085
search cancel

CA7 hung. Cannot login. Error REQSESS FAILED - RTNCD=X'10'(016) FDBK2=X'12'(018) SENSE=085

book

Article ID: 222916

calendar_today

Updated On:

Products

CA 7 Workload Automation

Issue/Introduction

CA 7 task goes in hung state and users are not able to logon and jobs are not getting submitted.

Cannot login to CA7.  Session manager fails with:
REQSESS FAILED - RTNCD=X'10'(016) FDBK2=X'12'(018) SENSE=085

ISPF interface gives the same error.

CA7ONL shows error:
CA-7.LOST - FOR VTM001
CA-7.V001 04 14 13 00000000 215635 VTM001  22 C I/O ERROR
CA-7.822 - (VTM001 ) CLOSED

Cause

After running CA 7 R12.0 for several months, upgraded the Datacom release to R15.0 the previous weekend.

Symptoms were the client could NOT log on.  No commands could be entered to CA/7.

This was NOT a VTAM or Network interface problem.

A review of the MUF for CA/7 shows messages:

 

DB00308I - LOG AREA IS 70% FULL, 13997 TRACKS SPILLABLE

DB00311I - LOG AREA IS  98% FULL, SPILLING TRACK NONE, OUT OF 19247
DB00311I - LOG AREA IS  99% FULL, SPILLING TRACK NONE, OUT OF 19497
*DB00311I - LOG AREA IS 100% FULL, SPILLING TRACK NONE, OUT OF 19996

The SPILL job had not been updated after the Datacom upgrade. 

Resolution

Automation needs to trap message DB00308I then execute job 

'hlq.CAL2JCL(AL2DBSPL)'

 

 

Additional Information

If CA 7 is hung,  issue the command '/F <ca7mufname>,STATUS' to determine the status of the Datacom MUF and CA 7 Queues.