Thanks Kirk,



We'll have to rearrange the library list and then try it again.



I appreciate everyone's time.



Thanks!



Jill



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kirk Goins
Sent: Thursday, August 27, 2009 4:58 PM
To: Midrange Systems Technical Discussion
Subject: Re: System-supplied output file QAIZACVN not valid



I've seen this before and QUSRSYS ahead of QSYS will cause this problem.







On Thu, Aug 27, 2009 at 1:38 PM, Jill Gallagher <JGallagher@xxxxxxxx> wrote:



The QSYS version has the SYSTEM SUPPLIED OUTFILE description. The library

list could be wrong. I didn't set it up so I'll have to talk to the person

who did. I do know that the QUSRSYS version was just created today, so the

command did do the create duplicate like the redpaper said it would. I'll

check on the library list issue though.







Thanks!







-----Original Message-----

From: midrange-l-bounces@xxxxxxxxxxxx [mailto:

midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx

Sent: Thursday, August 27, 2009 4:18 PM

To: Midrange Systems Technical Discussion

Subject: RE: System-supplied output file QAIZACVN not valid







When I do DSPLIBL (do NOT use EDTLIBL!!!!!) I see QSYS above QUSRSYS.







QSYS often has "shell" copies of data files. They are often copied by



these IBM utilities into QUSRSYS and then populated with data.







WRKOBJ QAIZACVN







Object Type Library Attribute Text



QAIZACVN *FILE QSYS PF SYSTEM SUPPLIED OUTFILE FOR



QAIZACVN *FILE QUSRSYS PF Output file for ANZOBJCVN







Which one has text like "system supplied outfile" which matches your error



message?



Perhaps it's trying to update the wrong one?







Sticking another library, like RBTSYSLIB above QSYS is not unheard of.



I've not heard of sticking QUSRSYS above QSYS though. Perhaps someone



buggered up WRKSYSVAL QSYSLIBL when adding RBTSYSLIB?







Rob Berendt



--



Group Dekko Services, LLC



Dept 01.073



Dock 108



6928N 400E



Kendallville, IN 46755



http://www.dekko.com























From:



Jill Gallagher <JGallagher@xxxxxxxx>



To:



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



Date:



08/27/2009 03:42 PM



Subject:



RE: System-supplied output file QAIZACVN not valid



Sent by:



midrange-l-bounces@xxxxxxxxxxxx















Kirb,















There's QUSRSYS and RBTSYSLIB before QSYS.















Jill















-----Original Message-----



From: midrange-l-bounces@xxxxxxxxxxxx [



mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kirk Goins



Sent: Thursday, August 27, 2009 2:38 PM



To: Midrange Systems Technical Discussion



Subject: Re: System-supplied output file QAIZACVN not valid















Jill Gallagher wrote:







Good afternoon,















We are attempting to run the ANZOBJCVN command on a V5R4 system and



received the CPFB0DE message "System-supplied output file QAIZACVN not



valid". I checked the archives and saw the message listed but not for



this reason. I also checked the "Getting Ready for i5/OS V6R1" and the



file layout for QAIZACVN on our system matches what is in the paper. Has



anyone else come across this issue and how did you resolve it?















TIA,







Jill















Jill Gallagher







United Consumer Financial Services







Sr. Systems Analyst







440-835-6612







jgallagher@xxxxxxxx<mailto:jgallagher@xxxxxxxx>































Jill, anything ahead of QSYS in the sysval QSYSLIBL?















--







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.















--



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.









--

Kirk

--

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.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.