• Subject: Re: whoami
  • From: ywexler@xxxxxxx
  • Date: Thu, 09 Jul 1998 08:34:05 +0300

Scott, Shadrach wrote:
> 
> I have 2 questions.
> 
> a) I need an RPG program I have written to be able to tell who is using
> it. In other words I need to retrieve the program callers userid. Is
> there an API I can use to do this? or a CL command? or ?
> 
> b) The second question stems from the first. I say I have written an RPG
> program, I have actually started on my second this morning. I am
> teaching my self RPG through the help of Judy Yaeger's book Programming
> in RPG/400 second edition. It has been a good book to start but I am
> ready for and RPG advanced features book or resource of some kind. I am
> curious what book(s) are the essential RPG programmers reference books.
> Do you just use the IBM RPG books that come on the softcopy CD-ROM or is
> there a second party book that if you are going to be an RPG programmer
> you gotta have.
> 
> As usual thanks for sharing your wisdom. It is greatly appreciated.
> 
> Shadrach Scott
> sscott@hiu.edu

Scott,
1. You can use the CL command: RTVJOBA. This cmd retrieves job
attributes like the name of the job and the user-id etc.
Your pgm run in the same job as the caller pgm.
To use this cmd within HLL pgm you must create a CL pgm.

2. The books in softcopy CD-ROM are OK for your purpose.

J. Wechsler
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].