|
1) When you start mirroring on ASP, which contains RAIDed drives, system will consider RAIDed drives already proctected and will leave them alone. Only non-RAID protected drives will be paired. In other words, if you have ASP containing only RAID-protected drives, starting mirroring for them will not change anything. If you really want mirrored protection, stop RAID-protection for drives in ASP, and then start mirroring. 4 and 5) QDBJRN (in QRECOVERY) is an internal system journal, which protects system dictionary files (QADBxxx). System takes care of this journal automatically, so normally user does not need to do anything about it. If you want to reset sequence numbers, try to do it in a restricted state. 6) When SMAPP is active (EDTRCYAP), system may write internal - invisible - entries to journals. These entries record changes to not-journaled access paths.These entries cannot be accessed by user, but they do consume sequence numbers. Best regards Alexey Pytel Dave Mahadevan <mahadevan@fuse.net> on 04/26/99 12:43:39 PM Please respond to MIDRANGE-L@midrange.com To: midrangel <MIDRANGE-L@midrange.com> cc: (bcc: Alexei Pytel/Rochester/IBM) Subject: Puzzling System Action Folks: First a few facts: I added 9337 EMC equivalent painted RAID 5 into a new asp on system running V3R2 with the latest cum ptf. I asked for mirror and it did Device Parity and when working DPY/Active. I copied a library into the new asp. It was done when there was almost no activity on the system. I checked the copied library. About two thirds were copied fine. The others had been copied with 0 records. History log showed that some these files with 0 records had been extended by at least one increment! No error messages on the log excepting some info messages on QDBJRN as follows. Size of member HPGMFILE increased 1 increments. Journal receiver QDBJRN0596 created in library QRECOVERY. Journal receivers QDBJRN0595 and *N detached. Sequence number not reset. First sequence number is 43625. Size of member MPENSION increased 1 increments. IPLed the system. Still records 0 in these files. Ok. Decided to get back to it later. Now did some updating on a file and added records to another file in a library in another asp. No commitment control. Records were added to one file but records were not updated on the second file. Added records did not show up on read but were in the file on a DSPPFM. I have access path maintenance set to *IMMED. No user complaints of any other updates etc. Completely puzzled. Asked for an IPL and went home. Checked the files after IPL, everything was updated and added records showed up on read. These files are not journaled. Decided to take no chance, ran QDBRCLXR and RCLSTG. No error messages. Message . . . . : Data base objects destroyed by reclaim storage operation. Cause . . . . . : 0 directories, 0 formats, and 0 recovery objects were destroyed by the reclaim storage operation. The data base objects that were destroyed either were damaged, or associated with damaged or destroyed data base files. RCLSTG processing complete. 105352 objects processed. 53 deleted. And about a dozen of the following before the RCLSTG message above: Journal receivers QDBJRN0612 and *N detached. Sequence number not reset. First sequence number is 180819. Journal receiver QDBJRN0614 created in library QRECOVERY. Journal receivers QDBJRN0613 and *N detached. Sequence number not reset. First sequence number is 196074. Questions: 1. Why did not the mirroring half the availalble disk space on the RAID5 asp? 2. Why did not the copy lib work on some files with no error messages (yes I checked thoroughly)? 3. Why did not the files update and added records show up (this program has been used hundreds of times and updated/added records show up immediately). 4. Although everything is ok now, I have a quezy feeling about this episode. What is the purpose of the QDBJRN? 5. How do I reset the sequence number on this QDBJRN. I used the CHGJRN with *GEN and *RESET which produced the following CPF7018: Additional Message Information Message ID . . . . . . : CPF7018 Severity . . . . . . . : 40 Message . . . . : Resetting sequence number not allowed. Reason code 1. Cause . . . . . : The sequence number for journal QDBJRN in library QRECOVERY cannot be reset because of reason code 1. The reason codes and their meanings follow: 1 -- A file being journaled to journal QDBJRN has changes that have not been forced to auxiliary storage, or one or more access paths are being journaled and either a clear physical file member (CLRPFM) command or a reorganize physical file member (RGZPFM) command is in progress for one or more of the members that the access paths are built over. I do have some files journaled. Does this required a restricted system? 6. Why did the sequence numbers on the QDBJRN jump by almost 100,000? 7. Anybody had good/bad experience with EMC HX3SR RAID5 (equivalent to 9337-242 & 9337-243)? I love EMC ... good and cost effective. Please reply your comments, criticisms, suggestions, words of wisdom, work arounds, workins, workouts etc. to the list so others can benefit too. :-) -- Thank You. Regards Dave Mahadevan.. mailto:mahadevan@fuse.net +--- | 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.