Scott
as previously mentioned
MUCH appreciated.
I've learned something new
The problem I am having (and now it makes sense) is that I am submitting a
job into a single thread jobq, which in turn tries to run the QSHEL
command. Hence the failure.
By the way the message id was QSH0002
Alan Shore
NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill
Scott Klement
<midrange-l@scott
klement.com> To
Sent by: Midrange Systems Technical
midrange-l-bounce Discussion
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
04/07/2008 04:21 Subject
PM Re: Qshell command
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
Alan,
An easier way than looking up the 3489 in that source member would've
been to type the following at the command line:
DSPMSGD CPE3489
However, I could not be certain what that message was in regards to,
since your job-log snipped omitted the text describing reason code 4. I
would've looked up the 2nd-level text of the message on my own system,
but your job log snippet also omitted the msgid.
But, any any rate, when you see a reference to 'errno', you can
generaally get a description of the error by typing DSPMSGD CPExxxx
where xxxx is the error number.
Alan Shore wrote:
Tommy (and obviously Scott Klement)
MUCH appreciated
Thanks
--
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.
midrange.com
