× 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 guys
I'm hoping someone can point out what I'm doing wrong
I am attempting to run a Qshell command within a CLP program, and its
failing. I'm drawing a complete blamk as to why, and I've been working on
Production problems since 2:30 a.m.
If anyone can help, it would be much appreciated.
Thanks in advance
I've posted part of the joblog below. I cant even find what errno 3489
means

Message . . . . : 23700 - QSH CMD('LS /Directory/Subdirectory/Extract
>/qsys.lib/prod.lib/filelist.file/m643364.mbr')
40 04/07/08 11:00:59.597432 QZSHQSHC QSHELL *STMT
LLABFTP1CL
From module . . . . . . . . : QZSHQSHC
From procedure . . . . . . : SendMsg__FPcT1Pvi
Job Log S1042267 04/07/08
11:00:59
LLABPROC User . . . . . . : COMPILE Number . . . . . . . . .
.
LLABPROCJD Library . . . . . : PRODPA
SEV DATE TIME FROM PGM LIBRARY INST TO PGM
Statement . . . . . . . . . : 2
Message . . . . : Error found with QSH session, reason code 4, errno
3489.
Cause . . . . . : The system detected an error with a QSH session,
reason
code 4, errno 3489. The reason codes and their meanings are as
follows: 1
Error found when starting a new QSH session. 2 - Error found when
running
an existing QSH session. 3 - Error found when ending an existing QSH




Alan Shore

NBTY, Inc
(631) 244-2000 ext. 5019
AShore@xxxxxxxx
"If you're going through Hell, keep going" - Winston Churchill

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.