Instead of changing the command default in QSYS, I would recommend that you create another library for changed IBM commands, copy the command to that library and change it there.
Then, use the CHGSYSVAL command to change the system portion of the library list to have your new library ahead of QSYS. That way, your command will be executed and the IBM command will not have been changed.
This is also good for documentation if you upgrade the OS as you will have all of your changed commands there so that you can redo the changes on the new release.
Jeff Young
Sr. Programmer Analyst
IBM -e(logo) server Certified Systems Exper - iSeries Technical Solutions V5R2
IBM Certified Specialist- e(logo) server i5Series Technical Solutions Designer V5R3
IBM Certified Specialist- e(logo)server i5Series Technical Solutions Implementer V5R3
________________________________
From: "elehti@xxxxxxxxxxxxxxxxxx" <elehti@xxxxxxxxxxxxxxxxxx>
To: midrange-l@xxxxxxxxxxxx
Sent: Friday, April 17, 2009 12:02:17 PM
Subject: RE: User joblogs
Dave,
In the CL program you run every day to change IBM's default system
settings to your custom settings, add these statements:
QSYS/CHGCMDDFT CMD(QSYS/SIGNOFF) NEWDFT('LOG(*LIST)')
QSYS/MONMSG MSGID(CPF0000 CPC0000 CPD0000)
Everyone who signs off will produce a joblog of their session unless
they prompt with F4 and change to *NOLIST.
As an Amazon Associate we earn from qualifying purchases.
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.