Re: DirPCServ error

Depends on how it's sent. If it's sent using RUNRMTCMD, check for a
spooled file that's created that contains the output (possibly error
information) of the command. If it's the rexec API, you can read the
socket and get the output information. I dunno about STRPCCMD.

On 10/17/07, Glenn Gundermann <ggundermann@xxxxxx> wrote:

Hi Mark,

It's not an issue of a command or program being locked. The command
CHKDIRMED when run comes back with a status of locked but I don't know what
that means.

Forgetting what package we're running in the background for the moment...

If the System i sends a command to the PC, where does it go? Is there a TCP
job I can check for the joblog, something I can turn system auditing on for,
a trace to do, etc.?

Tks,

Glenn Gundermann
ggundermann@xxxxxx
(647) 272-3295


----- Original Message -----
From: "Mark Allen" <scprideandms@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, October 16, 2007 8:07 PM
Subject: Re: DirPCServ error

Sorry, meant wrkobjlck on the cmd in that libray, might tell you if it is
locked and by who, since the other cmd you mentioned indicated is was
locked?

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