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




When I run commands in "normal" mode, the joblog appears in the "iSeries
Commands Log" view. (Use the RSE menu option [Windows|Show View|iSeries
Command Log] to show it.) "normal" mode appears to mean that the command
is run in the same batch job as the RSE. This doesn't work if the
command/program being run requires any user input other than parameters.

When run in "batch", the joblog is part of a created batch job instead.

When run in "interactive", you need to have an associated interactive
green-screen session running the STRRSESVR command.


Best regards,
Paul

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]
On Behalf Of David FOXWELL
Sent: 24 September 2008 08:13
To: Websphere Development Studio Client for iSeries
Subject: [WDSCI-L] Log of program run from RSE

Hi,

Can someone please explain to me the difference between normal and batch
when creating a set of commands under iSeries Commands in the RSE?

I have a command that does a CALL to a CLP and is being executed in mode
normal. I was wondering where can I find the log of the program, and
found 4 jobs QUSER/QZRCSRVS. Right clicking shows the log but you need
to find which QZRCSRVS and at the end of a long day the log will be a
lot more difficult to read. Is there another way?


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.