× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: Program Call Stack
  • From: "James W. Kilgore" <qappdsn@xxxxxxxxxxxxx>
  • Date: Wed, 29 Nov 2000 21:33:59 -0800
  • Organization: Progressive Data Systems, Inc.

Daniel,

Pass on to Susan that when a program is run interactively, the 'job" is the 
workstation
id, but when run in batch it's the job name.

If she is trying to determine the submitter of a batch job that's a bit 
different that
walking up the call stack in an interactive session.

Which does she need?

Daniel Keith wrote:

> A friend of mine needed some help on this. Any ideas?
>
> Daniel,
>
> Help!  Is there a way to retrieve the program's name that called the program
> that you are in (if it was ran interactively).  In the program data
> structure it looks like if the job was run interactively it puts the work
> station id.  If the job was run in batch it does give you the program's
> name.
>
> Do I make any sense?
>
> Thanks,
>
> Susan
>

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

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.