CEE3322C error message, user-abend 4038

[Dwa...@aol.com]

In a message dated 11/10/2003 9:12:41 AM Eastern Standard Time, metu...@co.ha.md.us writes:

CEE3322C

Mark:

       As per the manual:

1 (X'01')       The unhandled condition was a software-raised or  
                user-raised condition.  See output on SYSLST for  
                more information.                                 

       What was on SYSLST? Is this a COBOL program? What flavor of COBOL? Are the LIBDEFs correct for LE? What I suspect is that something tried to go over the 16M line but this program couldn't handle it!

David Wakser
Mnemotech

[turner, mark]

Greetings listers.  This past Friday, I changed the allocations for some of my static partitions, and I had one job cancel, and I'm hoping that someone can explain why this happened.

My BG partition, was defined as ALLOC BG=8M and SIZE BG=4M, and I changed it to ALLOC BG=14M and SIZE BG=4M.  When I did this, I had a job step cancel with the following:

4354 BG 0000 Z0812I CURRENT STEP NAME SET TO STEP2B  21:37:53 
4355 BG 0000    WER226A  END SYNCSORT (ISIDAILY), RECORD=        82, INCORE 
4356 BG 0000 CEE3322C EXECUTION ABNORMALLY TERMINATED WITH USER-ABEND CODE 4038 AND
              REASON CODE 0001.                                             
4357 BG 0000 0S02I A CANCEL OR CANCEL ALL MACRO WAS ISSUED                  
4358 BG 0000 0S00I JOB ISIDAILY CANCELED                                    
4359 BG 0000 0S07I PROBLEM PROGRAM  PSW = 071D0000 80200B58                 
4360 BG 0000 Z0402I ZEKE VAR $0VAR1           UPDATED                       
4361 BG 0000 Z0402I ZEKE VAR $0VAR2           UPDATED                       
4362 BG 0000 Z0402I ZEKE VAR $0VAR3           UPDATED                       
4363 BG 0000 Z0402I ZEKE VAR $0VAR4           UPDATED                       
4364 BG-0000 // PAUSE PRGRM ABEND OF ISIDAILY IN STEP2B PROG ISSF900 COND 0 

When I backed my changes out, this step ran fine.  The program description for ISSF900 is:

THIS PROGRAM INITIALIZES AND MAINTAINS THE DAILY ISIS FINANCIAL FILE. THE PROGRAM UTILIZES A CONTROL RECORD TO OBTAIN THE DEPOSIT CONTROL NUMBER.  ALL FINANCIAL RECORDS PRIOR TO AND INCLUDING THAT CONTROL NUMBER BASE (JULIAN DATE) ARE THEN STRIPPED FROM THE DAILY DATASET AND WRITTEN TO A DAILY DEPOSIT BACKUP DATASET. RECORDS WHICH CONTAIN A CONTROL NUMBER BASE GREATER THAN THE DEPOSIT CONTROL NUMBER CUTOFF REMAIN ON THE DAILY DATASET, AS WELL AS THE CONTROL RECORD. THESE REMAINING RECORDS ARE UNCHANGED BY THIS PROCESSING. A BACKUP OF REMAINING FINANCIAL RECORDS AND THEIR CONTROL RECORD IS TAKEN ALSO.

The corresponding JCL statements are as follows:                 

SET STEP STEP2B, PROCESS DAILY TRANSACTIONS                            
// ASSGN SYS004,230                                                    
// DLBL ISPFINB,'ISPFINB',,VSAM,CAT=SAMCAT,DISP=(OLD,KEEP),            C
               RECORDS=400,RECSIZE=120                                 
// DLBL ISSFIN,'ISSFIN',,VSAM,CAT=SAMCAT,DISP=(,KEEP),                       C
               RECORDS=400,RECSIZE=120                                 
// DLBL ISDEPST,'ISDEPST',,VSAM,CAT=SAMCAT,DISP=(,KEEP),               C
               RECORDS=400,RECSIZE=120                                 
// EXEC ISSF900,SIZE=(AUTO,128K)                                       
/*                                                                     
IF $MRC > 0 THEN                                                       
GOTO MRCEOJ                                                            

We're a native VSE shop, running VSE/ESA 2.5.1.

Thanks in advance.

Mark E.Turner
Systems Programmer
Harford County Government
45 S. Main St.
Bel Air, MD  21014

mailto:metu...@co.ha.md.us

Office: (410) 638-3213  Fax: (410) 893-2643

[Lamar, Dave]

Mark -

    As mentioned, check the listing. It must be intuitive, because that's all I have noted in my Messages and Codes manual.

 

Best of Luck.

Regards,

dl

---

From: owner...@Lehigh.EDU [mailto:owner...@Lehigh.EDU] On Behalf Of turner, mark
Sent: Monday, November 10, 2003 6:04 AM
To: VSE Discussion List
Subject: CEE3322C error message, user-abend 4038

[Diane Ramirez]

I received this error several years ago.  Upon searching the VSE L-Serv archives I learned that this abend occurs when there is too little storage, or the program is not run above the line.  Perhaps this will help you resolve the problem.

 

Diane Ramirez

Systems Programmer

Fuji Photo Film, USA  

>>> Dwa...@aol.com 11/10/03 09:18AM >>>

[Rbo...@aol.com]

Mark,

 

 

I'd have to ask the following questions:

 

1). Does the COBOL/VSE program issue any calls to subroutines, written in any language? What language/s? What is the AMODE/RMODE of these subroutines.

2). If call/s to any subroutines are done, does the COBOL/VSE program isue them STATICALLY or DYNAMICALLY?

3). What are your current LE/VSE settings for ALL31= and STACK=?

4). What are your current setting for the COBOL compiler options RENT, DATA, and RMODE?

 

Bob Botsis
Kroger Company
513.745.5487
rbo...@aol.com
(I read and I remember,
I do and I understand)

[gary....@escape.net.au]

Mark,

> Greetings listers. This past Friday, I changed the allocations for some
of
> my static partitions, and I had one job cancel, and I'm hoping that
someone
> can explain why this happened.
>
> My BG partition, was defined as ALLOC BG=8M and SIZE BG=4M, and I changed
it
> to ALLOC BG=14M and SIZE BG=4M. When I did this, I had a job step cancel
> with the following:
>
> 4354 BG 0000 Z0812I CURRENT STEP NAME SET TO STEP2B 21:37:53
> 4355 BG 0000 WER226A END SYNCSORT (ISIDAILY), RECORD= 82,
INCORE
>
> 4356 BG 0000 CEE3322C EXECUTION ABNORMALLY TERMINATED WITH USER-ABEND CODE
> 4038 AND
> REASON CODE 0001.
>
> 4357 BG 0000 0S02I A CANCEL OR CANCEL ALL MACRO WAS ISSUED
>
> 4358 BG 0000 0S00I JOB ISIDAILY CANCELED
>
> 4359 BG 0000 0S07I PROBLEM PROGRAM PSW = 071D0000 80200B58
>
> 4360 BG 0000 Z0402I ZEKE VAR $0VAR1 UPDATED
>
> 4361 BG 0000 Z0402I ZEKE VAR $0VAR2 UPDATED
>
> 4362 BG 0000 Z0402I ZEKE VAR $0VAR3 UPDATED
>
> 4363 BG 0000 Z0402I ZEKE VAR $0VAR4 UPDATED
>
> 4364 BG-0000 // PAUSE PRGRM ABEND OF ISIDAILY IN STEP2B PROG ISSF900 COND
0
>
>
>

> The corresponding JCL statements are as follows:
>
> SET STEP STEP2B, PROCESS DAILY TRANSACTIONS
> // ASSGN SYS004,230
> // DLBL ISPFINB,'ISPFINB',,VSAM,CAT=SAMCAT,DISP=(OLD,KEEP), C
> RECORDS=400,RECSIZE=120
> // DLBL ISSFIN,'ISSFIN',,VSAM,CAT=SAMCAT,DISP=(,KEEP),
> C
> RECORDS=400,RECSIZE=120
> // DLBL ISDEPST,'ISDEPST',,VSAM,CAT=SAMCAT,DISP=(,KEEP), C
> RECORDS=400,RECSIZE=120
> // EXEC ISSF900,SIZE=(AUTO,128K)

I'd lose the AUTO option here and replace it with ISSF900 instead. Will
waste less 24-bit GETVIS that way.

> /*
> IF $MRC > 0 THEN
> GOTO MRCEOJ
>
> We're a native VSE shop, running VSE/ESA 2.5.1.
>

I think you probably need PQ42620,PQ50085 and PQ69915 if you don't
already have them installed.
I would also point out that you should read the close information in
PQ66612 very carefully as well since this PTF will be included when
you order PQ69915. There have been some changes in the area of
blocked VSAM/SAM datasets and how the blocksize is extracted.

If you're using the supplied defaults for ALL31 and STACK then you
should be fine for LE option settings. These options only apply to
what the application is capable of not how big the partition is that
the program is running in.

Regards,
Garry Hasler
VM/VSE Systems Programmer
APC - Perth