Why does NMJAVAFW terminate unexpectedly with S422 or S322?

Products

• CMDB for z/OS
• NetSpy Network Performance
• NetMaster Network Automation
• SOLVE
• NetMaster Network Management for SNA
• NetMaster Network Management for TCP/IP
• NetMaster File Transfer Management
• SOLVE:Operations Automation
• SOLVE:Access Session Management
• SOLVE:FTS

Issue/Introduction

Why does NMJAVAFW terminate unexpectedly with S422 or S322?

Environment

Release:
Component: NETSPY

Resolution

Background: NMJAVAFW is an MVS started task. It spawns OMVS (Unix System Services) tasks. The second step of NMJAVAFW spawns a long running OMVS task. Most sites use IBM's default limit for CPU utilization, which is 30 minutes. Once the default limit is reached, NMJAVAFW terminates.

To avoid the S422 and S322 ABENDS, code TIME=1440 on the second step of the PROC. In effect, TIME=1440 sets NMJAVAFW's CPU limit to "no limit".

A sample update follows.
//*--------------------------------------------------------------------
//* Start the ReportCenter Java Application
//*--------------------------------------------------------------------
//NMJAVA EXEC PGM=BPXBATCH,REGION=0M,TIME=1440,
// PARM='SH ?/your-hfs-prefix2/nm/reporter/usr/adaptor/Adaptor.bat'