Portal | Manuals | References | Downloads | Info | Programs | JCLs | Master the Mainframes
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Usergroups Profile Log in to check your private messages Log in
 

 

PL/1 DB2 batch abend code 4093 reason 70

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> PL/I & Assembler
View previous topic :: :: View next topic  
Author Message
Chuck Shorter

New User


Joined: 11 Aug 2009
Posts: 2
Location: Charlotte, NC

PostPosted: Tue Aug 11, 2009 5:00 am    Post subject: PL/1 DB2 batch abend code 4093 reason 70
Reply with quote

Cannot find any "meaningful" abend code descriptions via Google that tell me what caused this abend code. Indications are that it's related to region memory or "insufficient GETVIS":
-------------------------------------
DB2 execution cards generated:
DSN SYSTEM(GIDD)
RUN PROGRAM(GEMSHP1) PLAN(GEMSHP1)
END
DSN ENDED DUE TO ERROR+
USER ABEND CODE 4093 REASON CODE 00000070
------------------------------------------------------------
The local shop "experts" (IBM/Maersk) can't seem to help me. On my JOB parameters, I've tried REGION=0M, 1M, 2M, 4M,20M,32M.
First PL/1 DB2 batch program I've written in quite a few years but it's a simple program -- fetch a LEFT OUTER JOIN cursor of rows from a shipment table to write an output key file of those rows selected for deletion by purge-date.
It's got to be something simple that I'm overlooking after so many years away from PL/1. Maybe a JCL problem:
----------------------------------------------
//UHCES4SP JOB 9037,'GEMS SHPNO PURGE',CLASS=D,MSGCLASS=0,REGION=4M,
// NOTIFY=UHCES4
//**-----------------------------------------------------------------*/
//** EXEC GEMSHP1 - SELECT SHIPNO RECS TO BE PURGED FROM GEMSSHIP */
//**-----------------------------------------------------------------*/
//GEMSHP1 EXEC IDBDDEXE,PROGRAM=GEMSHP1,PLAN=GEMSHP1
//STEPLIB DD DSN=U4GEMS.DEMO.SCLMLOAD,DISP=SHR
//SHPVRSN DD DSN=UHCES4.DEMO.SHPVRSN,DISP=(NEW,CATLG,DELETE),
// DCB=(RECFM=FB,LRECL=52),SPACE=(TRK,(10,2)),UNIT=SYSDA
//SYSUDUMP DD SYSOUT=*
//SYSPRINT DD SYSOUT=*
//SYSABEND DD SYSOUT=*
--------------------------------
If you can just point me to a (ref manual) website where I can get a description/remedy for this abend code 4093, I'd be much obliged.
Thanks,
Back to top
View user's profile Send private message

Robert Sample

Global Moderator


Joined: 06 Jun 2008
Posts: 8054
Location: East Dubuque, Illinois, USA

PostPosted: Tue Aug 11, 2009 5:14 am    Post subject:
Reply with quote

40xx codes tend to be Language Environment run-time messages. The LE 4093 RC=70 says
Quote:
X'70' (112)
A load module did not contain a main procedure/function and was invoked without Language Environment having been previously initialized.
Back to top
View user's profile Send private message
Terry Heinze

JCL Moderator


Joined: 14 Jul 2008
Posts: 1249
Location: Richfield, MN, USA

PostPosted: Tue Aug 11, 2009 6:14 am    Post subject:
Reply with quote

Looks like Robert pointed you in the right direction. Incidentally, GET VIrtual Storage is a VSE term, not MVS. See ftp://ftp.software.ibm.com/eserver/zseries/zos/vse/pdf3/wavv02/wavvGetVis.pdf
Back to top
View user's profile Send private message
Chuck Shorter

New User


Joined: 11 Aug 2009
Posts: 2
Location: Charlotte, NC

PostPosted: Tue Aug 11, 2009 8:00 pm    Post subject: re: PL/1 DB2 Batch abend code 4093 reason 70.
Reply with quote

icon_redface.gif Sorry, I saw the "insufficient GETVIS" comment in one of the many abend code descriptions that I googled. Didn't occur to me that it was out-of-context. I've been dealing with GETVIS problems in CICS/VSE off-and-on since the early '80s. Usually caused by "unenlightened" programmers who code CURRENT-DATE, ACCEPT DATE FROM, or DISPLAY in their CICS CMD COBOL programs, or compile them with STATE, FLOW options. I think some of these restrictions have been relaxed in later versions of CICS TS/v3. Always wondered why the CMD-level translator couldn't look for those restricted ops in the code and flag them.
Based on the abend code description, I thought maybe I had used a CICS "long-running" program (with No EXEC CICS code) as a model for my PL/1 DB2 Batch programs and missed changes to the OPTIONS, but the programs are now recompiled with plain OPTIONS(MAIN) and still getting the 4093. I'm going to get one of the "environment-savvy" locals to look at my JCL -- could be the PROC that I'm executing or the wrong STEPLIB. Thanks for the help.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> PL/I & Assembler All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts Job failing with USER = 4093 REASON C... Pradeepa S ABENDS & Debugging 1 Wed May 17, 2017 3:35 pm
No new posts COBOL Code Parsers and Lineage Establ... balimanja COBOL Programming 2 Tue May 02, 2017 3:30 am
No new posts Cobol upgrade - source code missing f... gthmrj IBM Tools 1 Wed Apr 26, 2017 6:04 pm
No new posts HLIST Utility In Batch Virendra Shambharkar TSO/ISPF 4 Fri Apr 07, 2017 3:38 pm
No new posts Batch job tuning sgandhla Testing & Performance analysis 5 Fri Mar 24, 2017 9:41 pm


Facebook
Back to Top
 
Mainframe Wiki | Forum Rules | Bookmarks | Subscriptions | FAQ | Tutorials | Contact Us