× 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.



Hi Mathieu,

For the sake of debugging, could you dump the call stack in PGM1? i.e. do something like this:

DSPJOB JOB(*) OUTPUT(*PRINT) OPTION(*PGMSTK)

If this is an RPG program, you can run that command via QCMDEXC or similar.

The point is, it'll show all of the programs in the call stack and which activation groups they are in. That should make it easier to see where the problem is occurring.


Mathieu Turcotte wrote:
Hi, I'm having a hard time with QTEMP and the activation group. Please
see the example below.


Job A in the IBM scheduler

call OUTBOUND (Pgm activation group: *CALLER)

OvrDbf FILE(FILEA) TOFILE(QTEMP/FILEA) OVRSCOPE (*ACTGRPDFN)

CALL PGM1 (Pgm activation group: *QILE)

Write to FILEA


Job B in the IBM scheduler

Call SBMPGM (Pgm activation group: *QILE)

SBMJOB XX RQSDTA('CALL SNLPGM (''OUTBOUND '')')

SNLPGM Pgm activation group: *QILE

CALL OUTBOUND Pgm activation group: *CALLER

OvrDbf FILE(FILEA) TOFILE(QTEMP/FILEA) OVRSCOPE
(*ACTGRPDFN)

CALL PGM1 (Pgm activation group: *QILE)

Write to FILEA


Qtemp is always the last library in the library list.


The job A writes to the file in qtemp.
The job B writes to the file in the first librairy in the list, not
QTEMP. The override doesn't work in job B. Why? I know how to fix this,
that's not the issue. I'd like to understand what's happening.

Mathieu Turcotte

Consultant T.I. / I.T. consultant



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.