|
>To clarify #7: PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(D) >Will cause system to start IPL from V3R2 release tapes. >Make sure keylock is in NORMAL position. > >Step 12.5 could be inserted here to reapply changes to IBM defaults >(commands, authorities, printer file defaults, subsystems, job queues, >routing entries, etc. etc.) that you may have made in the past, and if you >did you should have kept all these changes in a CL program (I have one >called RLSUPDCHG, I've seen others call it something like OS400CHGS, etc.). >Yes some people make changes in a library they place above QSYS. I don't >like that approach (sorry guys :-) ) because a) I don't really like having >a library above QSYS in the library list that someone else may place >surprises in, and b) If you do have your own versions of commands etc. >above QSYS they may not work after a release upgrade anyway (ie. you may >have to recreate a command, make a subsystem change different because IBM >may have added the same routing entry you used into QCMN or somewhere, etc.) >so why not just place all your changes in a CL program that will recreate >commands, add routing entries, change command defaults, change command >authorities, etc. > If you want to modify command defaults for IBM commands, we do not do so in QSYS. For example, if you want your printers to resume printing without having to respond to a message in QSYSOPR after adding paper, you can change the command default for CRTDEVPRT to PRTERRMSG(*INFO). We create a library called SYSMODS (others call it ALTQSYS) with AUT(*USE) specified. We modify QSYSLIBL to put this library in front of QSYS. We then use a program CRTDUPOBJ to copy the commands into SYSMODS and modify the command defaults using CHGCMDDFT. As long as the library is created AUT(*USE), you should not have a security exposure of unauthorized people putting things into or modifying commands in a library in front of QSYS. Charlie Massoglia, Massoglia Technical Consulting, Inc. PO Box 1065, Okemos, MI 48854, USA 517-676-9700 Fax: 517-676-1006 EMAIL: cmassoglia@voyager.net * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * This is the Midrange System Mailing List! To submit a new message, * * send your mail to "MIDRANGE-L@midrange.com". To unsubscribe from * * this list send email to MAJORDOMO@midrange.com and specify * * 'unsubscribe MIDRANGE-L' in the body of your message. Questions * * should be directed to the list owner / operator: david@midrange.com * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
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.