ca.portal.admin

Re: [IDMSVENDOR-L] Journal buffer waits

Discussion created by ca.portal.admin on May 23, 2007
I believe there is an accept sysversion into .... which could tell you
the CV# - perhaps then using a called-module 9with a hard-coded table
relating system # to a TEST/PROD literal), you could determine whether
you are in TEST or PROD



This is Chris Hoelscher and I approved this message!

Chris Hoelscher
Senior IDMS & DB2 Database Administrator Humana Inc
502-476-2538
choelscher@humana.com



The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you
receive this material/information in error, please contact the sender
and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: [IDMSVENDOR-L] Journal buffer waits
"If you're running local mode, I think the ACCEPT will return garbage.
If your prod and test CVs are running on different LPARs, you could use
the following to determine if you're running on prod or test by checking
the system name. The only reason we use it is to ensure our S-Ox
sensitive-data masking programs only run on our test systems.

Statements from COBOL prog:
01 SYS-MODULE PIC X(8) VALUE 'VNAVSYS1'.
01 SYS-NAME PIC X(8).

CALL SYS-MODULE USING SYS-NAME.

DISPLAY ' '
DISPLAY 'SYSTEM NAME ==> ' SYS-NAME
DISPLAY ' '

Called prog:
*
* PROGRAM WILL RETURN 8 CHARACTER FIELD CONTAINING THE CURRENT SYSTEM
* NAME (I.E. SYD9 OR SYD1)
*
LA 15,16 GET POINTER TO CVT
L 15,0(0,15) LOAD ADDRESS OF CVT
L 1,0(0,1) UPDATE POINTER TO LINK
MVC 0(8,1),340(15) MOVE SYSTEM NAME TO LINK
BR 14 RETURN TO CALLING PROGRAM
END

Outcomes