Dynamically determining your environment in a mainframe batch program 2

[weberm]

I am running IBM COBOL2 from a CICS/MVS mainframe environment. In CICS I can dynmically determine my environment (TEST v PROD) by invoking this function:

EXEC CICS ASSIGN
APPLID(APPLID-WS)
USERID(USER-ID-WS)
END-EXEC.

I'm curious if there were something similar one could use in a batch program...

 

[dneufarth]

weberm,

Batch regions carry the name of their job. Do the job names contain an identifier that indicates production of test?

Dave

 

[WMK]

Check out Gilbert Saint-Flour's program at:

http://mywebpages.comcast.net/gsf/tools/cob2job.txt

This will get you to the "jobname" (via a COBOL program).

The program at:

http://mywebpages.comcast.net/gsf/tools/cob2sys.txt

will get you "system" level information (e.g. system name, lpar name, etc)

Bill Klein

 

[weberm]

Batch regions carry the name of their job. Do the job names contain an identifier that indicates production of test?

We use the same name for test and production versions, but we use different PROC parameter values to indicate different instances, as it were. This is one for production, for example:

//MRWFIRXX JOB (46046,00000,,25),'MRW',CLASS=C  
//STEP01   EXEC PROC=COBIPROD,PROG=FIRAQXX