NSS question

2009-07-10 Thread Gentry, Stephen
Is it possible to have duplicate, active entries in the NSS?  (sort of a
trick question; it appears that we do.) 

See below:

 

*NSS 0014 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT 

*NSS 0059 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT

 

I am pretty sure I did this by restoring, using SPXTAPE, the NSS twice.


My question or assumption is that I thought, when a duplicate entry is
restored, it would flagged the existing

one as  purged/deleted/removable (what ever the correct term is). 

Could someone explain this?

Please and thank you.

Steve

 



Re: NSS question

2009-07-10 Thread Schuh, Richard
SPXTAPE LOAD can create multiple active entries. It is in the HELP for SPXTAPE.


Regards,
Richard Schuh






From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Gentry, Stephen
Sent: Thursday, July 09, 2009 1:45 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: NSS question

Is it possible to have duplicate, active entries in the NSS?  (sort of a trick 
question; it appears that we do.)
See below:

*NSS 0014 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT
*NSS 0059 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT

I am pretty sure I did this by restoring, using SPXTAPE, the NSS twice.
My question or assumption is that I thought, when a duplicate entry is 
restored, it would flagged the existing
one as  purged/deleted/removable (what ever the correct term is).
Could someone explain this?
Please and thank you.
Steve



Re: NSS question

2009-07-10 Thread Bob Bates
Yup, use Q NSS USERS GUICSLIB to see who is accessing which one and then PUR 
NSS xxx the one not being used. It's a cleanup I've done many times when I've 
restored all the NSS files and there were still some out there from before 
whatever happened that made me need to restore them.


Bob Bates
Enterprise Hosting Services

w. (469)892-6660
c. (214) 907-5071

This message may contain confidential and/or privileged information.  If you 
are not the addressee or authorized to receive this for the addressee, you must 
not use, copy, disclose, or take any action based on this message or any 
information herein.  If you have received this message in error, please advise 
the sender immediately by reply e-mail and delete this message.  Thank you for 
your cooperation.




From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf 
Of Gentry, Stephen
Sent: Thursday, July 09, 2009 3:45 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: NSS question

Is it possible to have duplicate, active entries in the NSS?  (sort of a trick 
question; it appears that we do.)
See below:

*NSS 0014 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT
*NSS 0059 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT

I am pretty sure I did this by restoring, using SPXTAPE, the NSS twice.
My question or assumption is that I thought, when a duplicate entry is 
restored, it would flagged the existing
one as  purged/deleted/removable (what ever the correct term is).
Could someone explain this?
Please and thank you.
Steve



Re: NSS question

2009-07-10 Thread Jim Bohnsack
Steve--Yes, it is possible to have duplicates and not have the older 
entry flagged as being to be purged.  I don't remember which one's have 
to be manually handled, perhaps the DCSS's.  I know that in resaving 
CMS, the older CMS NSS always get flags as being purged and will stay 
there in that state until the last user releases it.  I've forgotten the 
rules or reasons.  Alan Altmark explained this several years ago when I 
ran into the same problem.  Since then I've always made a point of 
purging the older one to make sure.


Jim

Gentry, Stephen wrote:

This is a multi-part message in MIME format.

--_=_NextPart_001_01CA00D6.21ED8C3B
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable

Is it possible to have duplicate, active entries in the NSS?  (sort of a
trick question; it appears that we do.)=20

See below:

=20

*NSS 0014 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT=20

*NSS 0059 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS MAINT

=20

I am pretty sure I did this by restoring, using SPXTAPE, the NSS twice.


My question or assumption is that I thought, when a duplicate entry is
restored, it would flagged the existing

one as  purged/deleted/removable (what ever the correct term is).=20

Could someone explain this?

Please and thank you.

Steve

=20


--_=_NextPart_001_01CA00D6.21ED8C3B
Content-Type: text/html;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable

html xmlns:o=3Durn:schemas-microsoft-com:office:office =
xmlns:w=3Durn:schemas-microsoft-com:office:word =
xmlns=3Dhttp://www.w3.org/TR/REC-html40;

head
meta http-equiv=3DContent-Type content=3Dtext/html; =
charset=3Dus-ascii
meta name=3DGenerator content=3DMicrosoft Word 11 (filtered medium)
style
!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Times New Roman;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
--
/style

/head

body lang=3DEN-US link=3Dblue vlink=3Dpurple

div class=3DSection1

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'Is it possible to have duplicate, active entries in =
the
NSS?nbsp; (sort of a trick question; it appears that we do.) =
o:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'See below:o:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'o:pnbsp;/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'*NSSnbsp;nbsp;nbsp;nbsp; 0014 NSSnbsp; Anbsp; =
0258
10/23 22:06:14 GUICSLIB DCSSnbsp;nbsp;nbsp;nbsp; MAINT =
o:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'*NSSnbsp;nbsp;nbsp;nbsp; 0059 NSSnbsp; Anbsp; =
0258
10/23 22:06:14 GUICSLIB DCSSnbsp;nbsp;nbsp;nbsp; =
MAINTo:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'o:pnbsp;/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'I am pretty sure I did this by restoring, using =
SPXTAPE, the
NSS twice.nbsp; o:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'My question or assumption is that I thought, when a
duplicate entry is restored, it would flagged the =
existingo:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'one asnbsp; purged/deleted/removable (what ever the =
correct
term is). o:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'Could someone explain =
this?o:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'Please and thank you.o:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'Steveo:p/o:p/span/font/p

p class=3DMsoNormalfont size=3D2 face=3DArialspan =
style=3D'font-size:10.0pt;
font-family:Arial'o:pnbsp;/o:p/span/font/p

/div

/body

/html

--_=_NextPart_001_01CA00D6.21ED8C3B--

  


--
Jim Bohnsack
Cornell University
(972) 596-6377 home/office
(972) 342-5823 cell
jab...@cornell.edu


NSS question

2009-07-10 Thread John Franciscovich
I am pretty sure I did this by restoring, using SPXTAPE, the NSS twice.

My question or assumption is that I thought, when a duplicate entry is
restored, it would flagged the existing

one as  purged/deleted/removable (what ever the correct term is).=20

Could someone explain this?


By default, SPXTAPE LOAD will load an NSS that may duplicate one that
is already active on your system. SPXTAPE will load the NSS from tape
with the same class that it was SPXTAPE DUMPed with. SPXTAPE was
intentionally designed to operate this way; we didn't want the code to
decide for you which of the 2 NSSes you really want to keep.

There is a NODUP operand that you can use to prevent SPXTAPE from loading
a file from tape the duplicates an existing file:

 NODUP
 prevents the loading of any file that would duplicate a file that already
 exists on the target spooling system queue. For additional information,
 see usage note 4.

Usage Note 4:

4.   When using the NODUP operand, the definition of duplicate depends on
 the type of file.

 For standard spool files and system trace files, duplicate means that
 all the file attributes of the file on the tape are identical to a file
 on the queue. This includes the time stamp for when the file was
 opened. An identical time stamp indicates that they are identical
 files. (If some files on the system have been imported from other
 systems, it is possible that files could have been created on both
 systems at exactly the same microsecond with all the same file
 attributes, but contain different data. However, this is not very
 probable.)

 For system data files other than system trace files, duplicate means
 that the file name, file type, and class of the file on the tape are
 identical to the file on the queue. In addition, for named saved system
 and saved segment files, class A (active) and class R (restricted)
 files of the same file name and file type are considered duplicate
 because they cannot exist on the system at the same time.

 A file that is found to be a duplicate is identified in the resulting
 volume log with DUP_FILE in the SEG_STAT field. The FILE field of this
 entry in the log contains the file ID of the file already on the
 system. If the file on the system is moved to a different queue or user
 ID, or its file attributes are changed (for example, its spool class),
 the file is no longer identified as a duplicate.

 The NODUP operand helps you recover if a system failure occurs while
 you are loading files from tape. If you add the NODUP operand to your
 selection criteria and reprocess all the tapes that have already been
 processed, all the files that loaded correctly before the system
 failure are skipped. However, even with NODUP specified, you may still
 receive duplicate files if you are loading the same file concurrently
 from more than one tape.

 Keep in mind when using the NODUP operand that as the number of files
 in the queue where the files are being loaded increases, the amount of
 processing required to load the files from the tape increases
 dramatically. Each file to be loaded is compared to every file in the
 queue. For example, if the queue contains 1000 files and 1000 files are
 to be loaded, the result is over one million comparisons.

 The consequence of loading duplicate files is more serious for system
 data files than for standard spool files. If the NODUP operand is not
 used when loading system data files (or all files) from a tape for
 which no dump log is available, you should check to make sure that
 duplicate files were not loaded.  If this happens, check the files to
 determine which should be kept and purge the unnecessary files.

John Franciscovich
z/VM Development


Re: NSS question

2009-07-10 Thread Gentry, Stephen
Ok, just read the HELP info.  Thanks.

Why does VM/CP/NSS/?  allow both entries to be active?  How does it know
which one to use?  First one it finds?

 



From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On
Behalf Of Schuh, Richard
Sent: Friday, July 10, 2009 8:56 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: NSS question

 

SPXTAPE LOAD can create multiple active entries. It is in the HELP for
SPXTAPE.

 

Regards, 
Richard Schuh 

 

 

 





From: The IBM z/VM Operating System
[mailto:ib...@listserv.uark.edu] On Behalf Of Gentry, Stephen
Sent: Thursday, July 09, 2009 1:45 PM
To: IBMVM@LISTSERV.UARK.EDU
Subject: NSS question

Is it possible to have duplicate, active entries in the NSS?
(sort of a trick question; it appears that we do.) 

See below:

 

*NSS 0014 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS
MAINT 

*NSS 0059 NSS  A  0258 10/23 22:06:14 GUICSLIB DCSS
MAINT

 

I am pretty sure I did this by restoring, using SPXTAPE, the NSS
twice.  

My question or assumption is that I thought, when a duplicate
entry is restored, it would flagged the existing

one as  purged/deleted/removable (what ever the correct term
is). 

Could someone explain this?

Please and thank you.

Steve

 



Re: NSS question

2009-07-10 Thread P S
On Fri, Jul 10, 2009 at 9:10 AM, Gentry, Stephen 
stephen.gen...@lafayettelife.com wrote:

  Ok, just read the HELP info.  Thanks.

 Why does VM/CP/NSS/?  allow both entries to be active?  How does it know
 which one to use?  First one it finds?

CP. And you've sort of answered the 2nd (of 4) questions yourself: it allows
both to be active because it *doesn't* know which one to use. It uses the
first one it finds.

Consider someone doing an SPXTAPE RESTORE and loading more NSS files than
they realized were on the tape: if it replaced the class A entries with the
ones from the tape, all hell would/could break loose. Far better to allow
the duplication and let you clean up the mess...