HP3000-L Archives

October 2016, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Scott Petersen <[log in to unmask]>
Reply To:
Scott Petersen <[log in to unmask]>
Date:
Mon, 24 Oct 2016 14:29:33 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (159 lines)
One other note about files listed in FPROTECT.  They must reside in the base
MPE partition, this was always LDEV 1.

I included a file that was NOT on LDEV 1 and it became a nightmare trying to
recover the machine. The system ran fine and booted up fine, but when I
attempted to RELOAD the machine, I had more GRAY hair fall out.

Scott Petersen

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Mark Ranft
Sent: Monday, October 24, 2016 2:15 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Please remoind me of what these are

The file FPROTECT.PUB.SYS lists all the files that MPE write protects or
locks at system startup.  If any of your not stored files are not included
there, then you may have an issue where you haven't stopped all the jobs and
sessions before your backup.  Unless you have True Online backup installed
or another similar offering like RoadRunner or Orbit, you may be missing
files that are required to run your applications. 


:l fprotect,2
ACCOUNT=  SYS         GROUP=  PUB     

FILENAME  CODE  ------------LOGICAL RECORD-----------  ----SPACE----
                  SIZE  TYP        EOF      LIMIT R/B  SECTORS #X MX

FPROTECT*          80B  FA          91         91   3       32  1  *


:print fprotect
{************************************************************************}
{* This is the list of file names START will open to protect them       *}
{* from restore and purge.                                              *}
{* Names should be UPPER case and fully qualified with delimiters.      *}
{* This file is intended to be changed by the development lab only.     *}
{* File is fixed format editor file.                                    *}
{* First character of { signifies a comment line.                       *}
{* Before the name there should be a character and a space.             *}
{* W signifies write protection -- you can't purge or modify the file   *}
{* P signifies purge protection -- you can't purge it but may modify it *}
{*                                                                      *}
{* The file FPROTECT.PUB.SYS is itself write protected.                 *}
{************************************************************************}
'W IDP.BOOTUP.SYS'
'W IOCLASSP.BOOTUP.SYS'
'W IOLDEVP.BOOTUP.SYS'
'W IOPATHP.BOOTUP.SYS'
'W IOVOLP.BOOTUP.SYS'
'W LOGP.BOOTUP.SYS'
'W MISCP.BOOTUP.SYS'
'W SPUINFOP.BOOTUP.SYS'
'W SYSFILEP.BOOTUP.SYS'
'W A1002AI.MPEXL.SYS'


Mark Ranft
Pro 3K

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On Behalf
Of Gsainc
Sent: Monday, October 24, 2016 9:42 AM
To: [log in to unmask]
Subject: Re: [HP3000-L] Please remoind me of what these are

The files listed as not being backed up due to being "open for writing" are,
generally speaking, files that are created by the OS at boot up - and are
nothing to be concerned about. 

One can consider them as "temporary permanent files" - sort of.

For transparency purposes, it may suit you to itemize these files in your
procedural documentation - apart from the output spool files whose names
will vary from backup to backup. 

Gilles Schipper
Sent via mobile
416-702-7900

> On Oct 24, 2016, at 9:26 AM, James B. Byrne
<[log in to unmask]> wrote:
> 
> Following our successful recovery from a lost disc drive last October
> 11 I am reviewing our backup and recovery procedures.  As with 
> anything that is seldom used when we exercised our recovery procedures 
> we discovered that things could be made a little clearer to those 
> unfamiliar with the process. Which was me mainly. And I wrote it all.
> 
> We cleared up many of the mysteries and misconceptions respecting our 
> daily database backup.  Now I am down to accounting for the files 
> listed below which are excluded from our weekend @[log in to unmask]@ STORE by virtue 
> of being open.  I am well aware that this is due to the fact that they 
> are in use by a running HP3000 system that is otherwise idle. Any of 
> these that absolutely must be backed up are no doubt captured when we 
> create a CSLT, which we try to do monthly.  However, I would like to 
> know which are backed up on a CSLT or simply discarded.
> 
> The HPSPOOL files are obviously connected to running jobs, including 
> the backup job itself.  Likewise the NMLGxxxx log files are in use by 
> a running system. The system library SL file I can identify. But the 
> rest I could find no reference for when searching. I would like to 
> have these annotated with their purpose and whether or not they are 
> backed up on a CSLT; or discarded and recreated as needed; or that I 
> have a problem.
> 
> /HPSPOOL/OUT/O1191 NOT STORED: FILE IS OPEN FOR WRITING
> /HPSPOOL/OUT/O1721 NOT STORED: FILE IS OPEN FOR WRITING
> /HPSPOOL/OUT/O2 NOT STORED: FILE IS OPEN FOR WRITING 
> /SYS/MPEXL/WGCONFIG NOT STORED: FILE IS OPEN FOR WRITING 
> /SYS/PUB/DSTLGTAB NOT STORED: FILE IS OPEN FOR WRITING /SYS/PUB/DSTLID 
> NOT STORED: FILE IS OPEN FOR WRITING /SYS/PUB/DSTRINS NOT STORED: FILE 
> IS OPEN FOR WRITING
> /SYS/PUB/DSTWELC1 NOT STORED: FILE IS OPEN FOR WRITING
> /SYS/PUB/DSTWELC2 NOT STORED: FILE IS OPEN FOR WRITING 
> /SYS/PUB/FPROTECT NOT STORED: FILE IS OPEN FOR WRITING /SYS/PUB/HPGID 
> NOT STORED: FILE IS OPEN FOR WRITING /SYS/PUB/HPGIDNX NOT STORED: FILE 
> IS OPEN FOR WRITING /SYS/PUB/HPUID NOT STORED: FILE IS OPEN FOR 
> WRITING /SYS/PUB/HPUIDNX NOT STORED: FILE IS OPEN FOR WRITING 
> /SYS/PUB/JMATFILE NOT STORED: FILE IS OPEN FOR WRITING 
> /SYS/PUB/JOBQFILE NOT STORED: FILE IS OPEN FOR WRITING 
> /SYS/PUB/LOADLIST NOT STORED: FILE IS OPEN FOR WRITING
> /SYS/PUB/NMLG0113 NOT STORED: FILE IS OPEN FOR WRITING /SYS/PUB/SL NOT
> STORED: FILE IS OPEN FOR WRITING
> 
> 
> Regards,
> 
> -- 
> ***          e-Mail is NOT a SECURE channel          ***
>        Do NOT transmit sensitive data via e-Mail Do NOT open 
> attachments nor follow links sent by e-Mail
> 
> James B. Byrne                mailto:[log in to unmask]
> Harte & Lyne Limited          http://www.harte-lyne.ca
> 9 Brockley Drive              vox: +1 905 561 1241
> Hamilton, Ontario             fax: +1 905 561 0757
> Canada  L8E 3C3
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2