|
While I agree it mildly frightens me we run a RCLSTG on all of our 400's prior to a full system save except our development machine. For some reason the RCLSTG takes an inordinate amount of time on our development machine. Our development machine is an 820-23A2. Running the RCLSTG has cleared up many a save. Here is a table of how long the RCLSTG takes in our shop: System Date of Length of Length of Length of Length of Length of Length of Length of Total Name Downtime RCLDLO RGZDLO RCLSTG SAVSYS NONSYS SAVDLO SAV of IFS Length 40S-2111 2000-11-17 39 1:19 2:00 2:15 6:14 720-206A 2000-11-17 45 13 40 1 4 1:45 730-2C6E 2000-11-17 8 8 4:29 28 2:50 5 13 8:24 830-23D1 2000-11-17 1 41 3 7:20 48 15:40 820-23A2 2000-11-17 --All Rcl's were skipped-- 15 5:08 16 1:13 - 720-206F 2000-11-17 4 10 1:57 12 1:07 6 7 3:44 But using the handy data area: Data area . . . . . . . : QRCLSTG Library . . . . . . . : QUSRSYS Type . . . . . . . . . : *CHAR Length . . . . . . . . : 200 Text . . . . . . . . . : Information from RCLSTG Value Offset *...+....1....+....2....+....3....+....4....+....5 0 '1000421 172721 ' 50 '1000422 105640 ' 100 'V4R4M0 GDISYS 102181M ' 150 ' ' Looks like 17.5 hours for the 820-23A2 System Tape Disk Primary Name Drive Size Usage 40S-2111 2.5GB 11.8G at 81% Runs the boss's Notes as a test machine - only use. 720-206A 25GB 29G at 43% Does all EDI, FTP, etc 730-2C6E 3590 160.7G at 63% Runs HUGE number of BPCS databases, payroll, accounting Percent CPU 7.8%. Upgrade sitting in computer room waiting for next downtime. We don't mess around with this one. 901 user profiles with previous sign on date 01-Oct or greater 544 user profiles with previous sign on date 05-Dec or greater 830-23D1 3590 ASP1:133G at57.7% Domino server for 800+ users. Mail and many notes databases. ASP2:327G at97% ADSTAR PC backup stored in QSYS library file system. 820-23A2 3570 161.6G at 75% Development machine - Domino test with only me as a user. Gee that IFS is big, I better clean out my mail file. Nah, it's only 958MB. 720-206F 25GB 26.9G at 74% A couple copies of BPCS. All running V4R5. All had current cum's, group PTF's and what not applied 11/17 and will continue to do so every 8 weeks. I don't have stats on our web 400 yet. Site ain't live. Rob Berendt ================== Remember the Cole! "Todd kidwell" <Todd.kidwell@3cc.co.wa To: <MIDRANGE-L@midrange.com> yne.mi.us> cc: Sent by: Subject: Re: QSYS objects on a full system save owner-midrange-l@midran ge.com 12/06/00 06:57 AM Please respond to MIDRANGE-L Adam, Have you tried running a Reclaim Storage. This will attempt to identify and fix any problems with damaged objects. This command needs to be run when the system is in a restricted state and can take several hours, depending on your system. To get an idea of how long it will run, you can display the QRCLSTG data area. If anyone has ever run the RCLSTG command on this system, this data area will contain the start and stop times of the last time it was run. HTH, Todd Kidwell (Netstar) AS/400 System Administrator (313) 224-0578 >>> "Adam Driver" <drivera@starcity.com.au> 12/06/00 12:56AM >>> Neil, In the joblog I mentioned before (from the operators session on DSP01) the next message after the error message I mentioned before is CPF3772 : "SAVSYS completed. One or more objects not saved". As you said, this is probably not an object we use. We only do a full system save once a month, in the middle of the night. It has taken me three months to get the operators to actually sign off with *LIST so I can see the joblog. I only knew there was a problem because the full system save started generating CPA3708 : "CPF3772 received during SAVSYS command. (C G)" and asking the operators for a response. In the three months this has been happening we've had no reported problems with OS/400. I think I'll just keep an eye on this and go ahead with the upgrade in a few weeks as planned. Many thanks for your help. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | 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.