MIDRANGE dot COM Mailing List Archive



MIDRANGE-L » February 2013

RE: Spool File



Sandeep,

If you are getting the detail you want from your
current logging level, then no change is needed.

To get a very complete job log, I typically specify:

Message logging: LOG
Level . . . . . . . . . . . . 4
Severity . . . . . . . . . . . 00
Text . . . . . . . . . . . . . *SECLVL

This produces a very detailed job log for debug and test.

To get even more detail, you can run the job in debug mode.

A more practical level for tracking critical production jobs
would be something like:

Message logging: LOG
Level . . . . . . . . . . . . 4
Severity . . . . . . . . . . . 00
Text . . . . . . . . . . . . . *MSG

And you would set Severity according to your requirements.


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sandeep Karadkar
Sent: Tuesday, February 19, 2013 9:13 AM
To: Midrange Systems Technical Discussion
Subject: Re: Spool File

Thanks Gary

I am using level 40

On Tue, Feb 19, 2013 at 7:21 PM, Gary Thompson <gthompson@xxxxxxxxxxx>wrote:

Sandeep,

I have used various ways (cpyspflf mainly) to copy spool file data and
am not aware of any standard iSeries log that tracks which spool files
have been copied.

Your current job log, depending on the level of detail you have
defined, will show these commands.

Maybe a custom user exit could be programmed, but I have no experience
with this.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:
midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Sandeep Karadkar
Sent: Tuesday, February 19, 2013 7:58 AM
To: midrange-l@xxxxxxxxxxxx
Subject: Spool File

Dear All,

Please advice me if i have copy Spool file from iseries to my desktop,

I want to know is there is any log shows you that you copied some
spool from iseries ?


---------------------------------------------------------
Thanks & Regards,

Sandeep Namdev Karadkar
------------------------------------------------------------
--
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.



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




--
------------------------------------------------------------
Thanks & Regards,

Sandeep Namdev Karadkar

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








Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact