RE: IFS Save

I think QNTC is implicitly ignored.  It's not only IXA, it's every PC in 
your organization.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 




"DeLong, Eric" <EDeLong@xxxxxxxxxxxxxxx> 
Sent by: midrange-l-bounces@xxxxxxxxxxxx
09/24/2003 08:52 AM
Please respond to
Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>


To
"'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
cc

Subject
RE: IFS Save






Shouldn't you also be omitting /QNTC?  Saves of QNTC are only supposed to 
be
for IXA servers, I think. 

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Steve Martinson [mailto:SMartinson@xxxxxxxxxxxxx]
Sent: Tuesday, September 23, 2003 1:41 PM
To: 'MIDRANGE-L@xxxxxxxxxxxx'
Subject: IFS Save


Al Barsa... this is right up your alley...

While doing a save of the IFS, the tape came to an end and we received the
following error(s).  We're already in discussions with IBM and are 
wondering
if anyone can offer some assistance.

Message ID . . . . . . :   CPDA09F       Severity . . . . . . . :   00

Message type . . . . . :   Information

Date sent  . . . . . . :   09/22/03      Time sent  . . . . . . : 13:14:12

Message . . . . :   An APAR condition has occurred in module Qp0fVLck. The

  reason number is 1.

Recovery  . . . :   Contact your service provider.  The job log may have

  additional information in it.  Provide your service provider with the
module 
  name and reason number returned in the message.  Also, a file system 
dump

  might aid the service provider.  Enter  "CALL QP0FPTOS *DUMP" on a 
command

  line, and press the Enter key. This will create a file system dump in a

  spooled file, with file type "QSYSPRT" and user label "QP0FDUMP". 
Provide

  this dump listing to your service provider.  However, if there is an

  exception condition in the system, the file system dump request may not

  complete successfully. 

Leading up to the problem was an end-of-tape:
      15000 - SAV DEV('/QSYS.LIB/MAG01.DEVD') OBJ(('/*') ('/QSYS.LIB' 
*OMIT)

       ('/IMAGES' *OMIT) ('/QDLS' *OMIT)) SAVACT(*SYNC) OUTPUT(*PRINT)

       ENDOPT(*UNLOAD) INFTYPE(*ERR) CLEAR(*ALL)

     End of volume detected for file QSYSTAP in QSYS.

   ? G

     End of volume detected for file QSYSTAP in QSYS.

   ? G

     An APAR condition has occurred in module Qp0fVLck.  The reason number
is 
       1.

     An APAR condition has occurred in module Qp0fVLck.  The reason number
is 

*** This message loops from here on down to eternity...  many, many
joblogs!!!

In addition, ending the job abnormally results in the locking of IFS 
stream
files which are then "unlockable"...

Best regards,

Steven W. Martinson, CISSP
Manager of Outlink Security
Jack Henry & Associates, Inc.
7800 Willowchase Blvd.
Houston, TX.  77070
     voice                               281.517.8000
     external fax                281.517.8157
     internal ext                471800

<mailto:smartinson@xxxxxxxxxxxxx <mailto:smartinson@xxxxxxxxxxxxx> >


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.