Shmuel, thanks for the validation.

In our fairly large shop's early days, there was more communication between 
software and applications folks. Coding like this would not have moved forward 
at all. But now we find out about these little "gems", way too late in the 
application development cycle. A few industrious programmers come up with this 
stuff, simply trying to address their function requirements, but obviously need 
guidance. For every such gem, there's another 10 lurking out there. We're 
trying to scope this out, contain it as best we can. And yes, while RDJFCB 
might be the only way to get specific data, Walt's comment is bang on.

On the security side, we'll have to engage our DBAs. But on issues like getting 
the jobid of the caller, I don't suppose somebody knows of a list/index of 
system calls to provide access to stuff like that ? If we can tighten the 
process and steer people to use APIs, then I would feel like the appl code is 
significantly more insulated from software changes.


Stan
mailto:[email protected]
(613) 941-8091


-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of 
Shmuel Metz (Seymour J.)
Sent: June 24, 2011 10:37 AM
To: [email protected]
Subject: Re: Obtaining System Information from a COBOL program

In <[email protected]>,
on 06/24/2011
   at 08:50 AM, "Haynes, Stan" <[email protected]> said:

>The COBOL program has a static mapping of TCB and TIOT in the LINKAGE
>section. It gets the TIOT address from the TCB, then scans the TIOT,
>looking for a specific DDNAME.  It then calls an assembler program to
>do the RDJFCB for that DDNAME.

I have the same question as Walt: why not just do the RDJFCB?

>>>>      LA    4,36(4)          INC PTR TO EXIT LIST AREA  

Why? That just makes the code harder to read.

SAVEXIT  EQU   *                                                
         L     4,DCBADDR
         LA    9,EXLIST           LIST ADDRESS IN R9 IN DCBEXLST
         STCM  9,7,37(4)

>The instruction "LA  4,36(4)" concerns me (hard-coded offset). 

Indeed. The DCBD macro has been available for lo these many decades.
 
-- 
     Shmuel (Seymour J.) Metz, SysProg and JOAT
     ISO position; see <http://patriot.net/~shmuel/resume/brief.html> 
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Reply via email to