JCLNEAT drops the parameters from the JOB statement when the Account info is null.
Input to JCLNeat:
IN //JOBCARD JOB ,'..................',CLASS=2,MSGLEVEL=(1,1),MSGCLASS=L
IN //*---------------------------------------------------------------------
IN //* JCLCHECK TEST
Output:
OUT //JOBCARD JOB 0000
OUT //**------------------------------------------------------------------* 0000
OUT //** * 0000
OUT //*---------------------------------------------------------------------0000
Release: 12.0
Component: JCLCheck Workload Automation
Apply PTF SO03881.
++PTF (SO03881)
/*****************************************************************************
The following items are included in this solution:
1. JCLNEAT MEMORY LEAK
2. JCLNEAT BAD FORMAT WHEN JOBCARD MISSING ACCT
==========================================================================
JCLNEAT MEMORY LEAK
PROBLEM DESCRIPTION:
When processing a large number of JCL elements (jobs, procedures, copybooks,
and / or include files) JCLNeat is not properly managing memory utilization
which will lead to memory exhaustion as evidenced by a number of memory
related ABEND codes: S80A, S878, and U1008.
SYMPTOMS:
CA JCLNeat batch job can ABEND with S878-10, S80A-10, U1008, and/or other
memory related error codes.
IMPACT:
JCLNeat job is terminated prior to completion.
CIRCUMVENTION:
Reduce the number of JCL elements being processed.
JCLNeat runtime option JOBF=N may be used to bypass JOB statement formatting.