|
Neil, Thankyou. I wasn't planning a RSTOBJ for a damaged system object, I just knew the SAVSYS that runs at the beginning of a full system save was skipping an object in QSYS and I ws trying to find out what. I'm planning to upgrade to V4R4 in the next few weeks anyway. Would you think it wise to reinstall V4R3 first and make sure there is at least a decent SAVSYS of this level? Am I likely to run into problems with the upgrade if I have a damaged system object? Thanks Adam Driver Star City Sydney, Australia "Neil Palmer" <neilp@dpslink.com> on 05/12/2000 17:02:44 Please respond to MIDRANGE-L@midrange.com To: MIDRANGE-L@midrange.com cc: (bcc: Adam Driver/SC/StarCity) Subject: Re: QSYS objects on a full system save Adam, What you are referring to are just the tape labels, they are not object names from QSYS. As you surmized they do refer to the Licensed Program Number plus the VRM. The next 2 digits are the last two digits of the language code (24 = 2924 = English Upper/Lower case). The last 4 digits are just a sequence # for the LPP files on tape. If your objective is to try a RSTOBJ for a damaged system program in QSYS it won't work, unless you're prepared to also go into DST, Display/Alter Storage, and patch the System Entry Point table. When the system is installed or a release upgrade is done, the system entry point table is updated to contain a reference to system objects by address. If you just did a RSTOBJ the address for the object in the S.E.P.T. would be incorrect. If you have damaged QSYS objects the recommended method is to reinstall the operating system. (Not all the LIC & program products, just the operating system). A manual IPL will get you to the menu with the choices to IPL the system, Install the Operating System, or use Dedicated Service Tools. After the operating system is reinstalled you need to reapply the latest cum PTF package, and any other PTF's for 5769SS1 you may have downloaded. Neil Palmer DPS Data Processing Services Canada Ltd. 50 Acadia Avenue, Ste.102 AS/400~~~~~ Markham, Ontario, Canada. ____________ ___ ~ Phone:(905) 474-4890 x303 |OOOOOOOOOO| ________ o|__||= Cell.:(416) 565-1682 x303 |__________|_|______|_|______) Fax: (905) 474-4898 oo oo oo oo OOOo=o\ mailto:NeilP@DPSlink.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ http://www.DPSlink.com iSeries 400 The Ultimate Business Server "Adam Driver" <drivera@starcity.com.au> Sent by: owner-midrange-l@midrange.com 2000/12/04 23:24 Please respond to MIDRANGE-L To: MIDRANGE-L@midrange.com cc: Subject: QSYS objects on a full system save Hi Everyone, On a DSPTAP report from a full system save (option 21 from save menu) there are a group of objects listed, all starting with Q, that come before the list of libraries saved. As I understand it, these are various objects in QSYS that are saved in a particular way so the system can be restored from this tape. We have one object that caused errors and all I know from the joblog is the file seq number (29). Correct me if I'm on the wrong path here, but we had one save fall over and then a successful save. The joblog for the unsuccessful save says "Output tape for file QSYSTAP in library QSYS could not be closed normally after at least 0 blocks were written in file sequence number 29. Ending labels, tape marks, or both may be missing from the volume." (There is an entry earlier in the job log that says the tape was successfully initialised). I did a DSPTAP after the second successful save and file sequence number 29 is an object called Q5769SS1430240006. I guessed this is LICPGM (5769SS1) plus version (430). Is there any way to tell what the 240006 is? Would the same object in QSYS be saved in the same sequence with successive full system saves? Am I on the right track? (Is this just perhaps something stupid like the operators using old tapes?) Thanks in advance Adam Driver Star City Sydney, Australia
"Adam Driver" <drivera@starcity.com.au>
Sent by: owner-midrange-l@midrange.com 2000/12/04 23:24
|
To: MIDRANGE-L@midrange.com cc: Subject: QSYS objects on a full system save |
______________________________________________________________________ This document should only be read by those persons to whom it is addressed and is not intended to be relied upon by any other person. Accordingly, Star City disclaims all responsibility and accepts no liability (including in negligence) for the consequences for any other person acting, or refraining from acting, on such information prior to the receipt by those persons of subsequent written confirmation. If you have received this document in error, please notify our Helpdesk immediately by telephone on 61 2 9657 9797. Please also destroy and delete the document from your computer. Copyright Star City Pty Ltd. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and/or publication of this document and its contents is strictly prohibited.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.