Re: Log of program run from RSE

That affects whether the commands within the CL are logged when the job is set to LOGCLPGM(*YES), not whether messages or the calling command are logged. The messages, which are what I thought David was looking for, will be there unless the program is explicitly coded to remove them. In any event, whatever goes to the joblog and gets through the logging level filter should show up in the iSeries Commands Log in WDSCi for 'normal' commands, including those run ad hoc from the command box, which I think is what David was asking about.

Dave Shaw
Mohawk Industries

----- Original Message ----- From: <MichaelQuigley@xxxxxxxxxx>
To: <wdsci-l@xxxxxxxxxxxx>
Sent: Wednesday, September 24, 2008 2:06 PM
Subject: Re: [WDSCI-L] Log of program run from RSE

It can also not log the programs called if the called CL is compiled with
'LOG(*NO)'

wdsci-l-bounces@xxxxxxxxxxxx wrote on 09/24/2008 01:00:03 PM:

----- Message from "Dave Shaw" <daveshaw@xxxxxxxxxxxxx> on Wed, 24
Sep 2008 08:18:20 -0400 -----

To:

"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>

Subject:

Re: [WDSCI-L] Log of program run from RSE

David,

Why do you think they're different? The 'command log' is just a
representation of the RSE connection job's joblog. If your program runs

in

that job, which programs executed by 'normal' commands should do, then

its

messages will go to that log. If you're not getting everything, it may

be

due to the logging level of that job's job description - try executing a

chgjob log(4 0 *n) from the command line and see if it makes a

difference.

If it does, find the job description and change it.

Dave Shaw
Mohawk Industries