|
As Rob pointed out, you may be running an initial program that sets the
library list. Work management on the IBM i is a complex business. Do
a
DSPUSRPRF on the user profile in question. See what its job
description
is. Then do a DSPJOBD on that job description to determine the initial
library list.
An empirical way to check is to create a scheduled job entry with a bad
command that you know will hard halt. For example, call a program that
doesn't exist:
ADDJOBSCDE USER(MYUSER) CMD(CALL BADLIB/BADPGM)
When that runs, it will get hung in a MSGW. At that point, look at the
job and see what its library list is.
Joe
here's some informations about the way i scheduled the job :appears in
I scheduled the job with the login of the owner of MSGQ
When i DSPLIBL with the login of the owner of MSGQ, the library
the list
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.