Re: Preserving SFS last reference date across a restore
Yesterday I got a private note from Susan Farrel. And so I tested again: and I was proven wrong (or a bit wrong that is) - FILEPOOL BACKUP/RESTORE preserves all dates - FILEPOOL UNLOAD/RELOAD does not (the last-ref date is wrong) So, I'm surprized that the most recent tool is less good than the old one that exists since VM/SP R6 days. At the other hand, we already started installing HiDRO too. But I don't know if we will ever use it as we are somewhat in a hurry. And, FILEPOOL BACKUP/RESTORE also transparantly backups/restores files migrated by DFSMS. Does HiDRO supports that too? Kris, IBM Belgium, VM customer support Imler, Steven J [EMAIL PROTECTED] Sent by: VM/ESA and z/VM Discussions VMESA-L@LISTSERV.UARK.EDU 2006-03-10 17:25 Please respond to VM/ESA and z/VM Discussions To VMESA-L@LISTSERV.UARK.EDU cc Subject Re: Preserving SFS last reference date across a restore Kris, If you run (VM:Backup) HiDRO ... All three dates for *files* are preserved when they are restored. The only date that end up to be the date of the restore/rebuild are the Create_Date for Directories. This is because they are restored by issuing the CREATE DIRECTORY COMMAND. JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Kris Buelens Sent: Friday, March 10, 2006 08:22 AM To: VMESA-L@LISTSERV.UARK.EDU Subject: Preserving SFS last reference date across a restore This weekend we have to regenerate an SFS filepool that became much too b= ig. As we do have processes that use the file creation and last reference dates, so we'd like to preserve them. When we tested this quite some mon= ths ago we found a problem: - when we use VM:Backup to do a full restore, the creation date is kept, but the lastref date is set to the restore date. - when using FILEPOOL BACKUP/RESTORE, the last reference date is kept but the creation date gets set to the restore date. My idea was to save the dates of all files (we have this ready) and using= DMSOPCAT, DMSRDCAT and DMSWRCAT to restore the last reference date. But when I open the catalog for FILESPACE with intent READ, DMSRDCAT returns = the records in which I can find all file dates, but a DMSWRCAT is forbidden (= csl reasoncode 56400); if I open the catalog for FILESPACE with intent WRITE,= a DMSRDCAT directly fails with reason 56400. So, I am stuck. ANyone knows a solution? Kris, IBM Belgium, VM customer support
Re: Preserving SFS last reference date across a restore
HiDRO supports preserving the "migrated shell" for each file that has been migrated. Therefore after you RESTORE/REGENERATE your FilePool(s), touching a migrated file will trigger the RECALL mechanism of DFSMS as you would expect. When HiDRO backs up a FileSpace that contains migrated objects, a message is put out stating that particular domain contains one or more migrated objects. JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] On Behalf Of Kris BuelensSent: Tuesday, March 14, 2006 06:25 AMTo: VMESA-L@LISTSERV.UARK.EDUSubject: Re: Preserving SFS last reference date across a restore Yesterday I got a private note from Susan Farrel. And so I tested again: and I was proven wrong (or a bit wrong that is) - FILEPOOL BACKUP/RESTORE preserves all dates - FILEPOOL UNLOAD/RELOAD does not (the last-ref date is wrong) So, I'm surprized that the most recent tool is less good than the old one that exists since VM/SP R6 days. At the other hand, we already started installing HiDRO too. But I don't know if we will ever use it as we are somewhat in a hurry. And, FILEPOOL BACKUP/RESTORE also transparantly backups/restores files migrated by DFSMS. Does HiDRO supports that too? Kris,IBM Belgium, VM customer support "Imler, Steven J" [EMAIL PROTECTED] Sent by: VM/ESA and z/VM Discussions VMESA-L@LISTSERV.UARK.EDU 2006-03-10 17:25 Please respond toVM/ESA and z/VM Discussions To VMESA-L@LISTSERV.UARK.EDU cc Subject Re: Preserving SFS last reference date across a restore Kris,If you run (VM:Backup) HiDRO ... All three dates for *files* arepreserved when they are restored. The only date that end up to be thedate of the restore/rebuild are the Create_Date for Directories. Thisis because they are "restored" by issuing the CREATE DIRECTORY COMMAND.JR (Steven) ImlerCASenior Software EngineerTel: +1 703 708 3479Fax: +1 703 708 3267[EMAIL PROTECTED]-Original Message-From: VM/ESA and z/VM Discussions [mailto:[EMAIL PROTECTED] OnBehalf Of Kris BuelensSent: Friday, March 10, 2006 08:22 AMTo: VMESA-L@LISTSERV.UARK.EDUSubject: Preserving SFS last reference date across a restoreThis weekend we have to regenerate an SFS filepool that became much toob=ig. As we do have processes that use the file creation and last referencedates, so we'd like to preserve them. When we tested this quite somemon=thsago we found a problem: - when we use VM:Backup to do a full restore, the creation date iskept, but the lastref date is set to the restore date. - when using FILEPOOL BACKUP/RESTORE, the last reference date is keptbut the creation date gets set to the restore date. My idea was to save the dates of all files (we have this ready) andusing=DMSOPCAT, DMSRDCAT and DMSWRCAT to restore the last reference date. Butwhen I open the catalog for FILESPACE with intent READ, DMSRDCAT returns=therecords in which I can find all file dates, but a DMSWRCAT is forbidden(=cslreasoncode 56400); if I open the catalog for FILESPACE with intentWRITE,= aDMSRDCAT directly fails with reason 56400.So, I am stuck. ANyone knows a solution?Kris,IBM Belgium, VM customer support
ITO parameterfor LPR link
Hi, From what I see from examples, etc it seems that for an LPR link, the ITO parameter is always set to 0. Each time a file is printed there a bunch of messages and the link becomes inactive. I assume this is because of the ITO parameter, correct? For example : RSCS RDR FILE 2745 SENT FROM MIKE PRT WAS 4192 RECS 0017 CPY 001 A NOHOLD NOKEEP RSCS DMTAXM101I File 2745 (2745) enqueued on link IPDELOR RSCS DMTCMY700I Activating link IPDELOR LPR line= class=* queueing=priority RSCS DMTLPR012I Link IPDELOR exit routine LPRXONE loaded at 00F76140 RSCS DMTLPR181I Link IPDELOR ready for session initiation RSCS DMTAXM109I File queue reordered RSCS DMTLPR193I Link IPDELOR connecting to host 10.161.58.231 port 515 printer RAW RSCS DMTLPR146I Sending file 2745 (2745) on link IPDELOR from DEVVM(MIKE), records 17 RSCS DMTLPR147I Sent file 2745 (2745) on link IPDELOR to IPDELOR(SYSTEM) RSCS 001 FILE PURGED RSCS DMTAXM105I File 2745 purged RSCS DMTLPR193I Link IPDELOR disconnecting from host 10.161.58.231 port 515 printer RAW RSCS DMTLPR570I Link IPDELOR now set to deactivate RSCS DMTLPR183I Link IPDELOR session terminated RSCS DMTMAN002I Link IPDELOR deactivated RSCS DMTAXM109I File queue reordered If ITO is set to something different what is the effect? Does it tie up the printer? Mike Trying To Understand Horlick
ITO parameterfor LPR link
From what I see from examples, etc... it seems that for an LPR link, the ITO parameter is always set to 0. Each time a file is printed there a bunch of messages and the link becomes inactive. I assume this is because of the ITO parameter, correct? Correct this cause's the link to automatically terminate when there are no more files to process. AUTOSTART linkdefine parameter is what cause's the link to start when a file is queue to it. If ITO is set to something different what is the effect? Does it tie up the printer? For an LPR link, the connection with the printer is terminated however the link remains active for that time period. Best Regards, Les Geer IBM z/VM and Linux Development
Re: VM/ESA 2.4 under z/VM 5.x
On Mar 14, 2006, at 10:51 PM, Alan Ackerman wrote: I hope you can find someone who has tried it. We haven't tried it. It certainly isn't supported. What hardware are you planning to run on? VM does not virtualize everything (in fact, cannot). z/VM 5.x is supported o nly on zSeries and System z9. VM/ESA 2.4.0 does not (officially) run on a z9. You could certainly run it under Hercules under z/Linux, although there are probably licensing issues, since presumably VM/ESA 2.4 is not licensed to *that* processor. Adam
