× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Going to try and do one tonight we let y'all know

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jim Franz
Sent: Tuesday, May 06, 2003 9:09 AM
To: Midrange Systems Technical Discussion
Subject: Re: Errors in Nightly save after upgrade to V5R2 -UPDATE


have you run a RCLSTG since upgrade? (I know it was recommended in error
log for reason 1 & yours is reason 2, but it wouldn't hurt.) jim

----- Original Message -----
From: "Mark Allen" <mallen@xxxxxxxx>
To: "'Midrange Systems Technical Discussion'" <midrange-l@xxxxxxxxxxxx>
Sent: Tuesday, May 06, 2003 8:31 AM
Subject: RE: Errors in Nightly save after upgrade to V5R2 -UPDATE


> I did find (using Google) that PTF SI06157 was issued for this error 
> but it is already applied.
>
> http://www-912.ibm.com/a_dir/as4ptf.NSF/b3cb9d42f672b70f86256739004afa
> 0f
> /3ed14cfe1fe91da586256c4d0047f4ac?OpenDocument
>
> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Allen
> Sent: Tuesday, May 06, 2003 8:19 AM
> To: midrange-l@xxxxxxxxxxxx
> Subject: Errors in Nightly save after upgrade to V5R2
>
>
> Since doing upgrade to V5R2 we are getting the following error during 
> nightly save, doesn't stop the save but it is extending the save 
> window by about 45 minutes or so.  We are doing nightly backup via GO 
> BACKUP and saving Config, security data all user libraries and all 
> folders. It "appears" this msg is occuring during/right after the save

> of security, config, QPFRDATA,QRCL (which appears to be the culprit as

> all the messages refer to different objects in it), QSYS2, QUSRSYS and

> folders.
>
> Any ideas what the problem is and how to fix?  Is it a sympton of a 
> MUCH bigger problem.  All the messages are basicvally the samer except

> for the Object referenced in QRCL.
>
>                          Additional Message Information
>
>
>
>  Message ID . . . . . . :   CPF32A6       Severity . . . . . . . :
60
>
>  Message type . . . . . :   Information
>
>  Date sent  . . . . . . :   05/06/03      Time sent  . . . . . . :
> 01:26:43
>
>
>  Message . . . . :   Cross-reference notification 70 for request 1,
> problem
>    type 2.
>
>  Cause . . . . . :   A problem was detected while processing the
system
>
>    cross-reference files.  The problem type is 2.
>
>      The problem types and their meanings follow:
>
>      0 -- Context recovery
>
>      1 -- Inconsistent data was discovered in the cross-reference 
> files for
>    library QRCL. The system may not allow operations to objects in 
> library
>    QRCL.  The SQL catalogs may not be up to date. The system may not 
> allow
>    constraints to be added or removed.  The system may not allow 
> triggers to be
>    added or removed.
>
>      2 -- An unexpected condition was encountered
>
>
> More...
>  Press Enter to continue.
>
>
>
>                          Additional Message Information
>
>
>
>  Message ID . . . . . . :   CPF32A6       Severity . . . . . . . :
60
>
>  Message type . . . . . :   Information
>
>
>
>      3 -- Exit condition
>
>  Recovery  . . . :   If the problem type is 1, request a reclaim
storage
>
>    (RCLSTG command specifying SELECT(*ALL) or SELECT(*DBXREF) )
>
>  Technical description . . . . . . . . :   Additional information:
>
>      - Problem Type           : 2
>
>      - Request                : 1
>
>      - Instance               : 70
>
>      - IASP/ASP Number        : 0
>
>      - Failing Context        : QRCL
>
>      - Object Context         : QRCL
>
>      - Object Name            : Q752h%-k
>
>      - Cross-reference Context: QSYS
>
>      - Cross-reference File   : QADBXREF
>
>
> More...
>  Press Enter to continue.
>
>
>
>                          Additional Message Information
>
>
>
>  Message ID . . . . . . :   CPF32A6       Severity . . . . . . . :
60
>
>  Message type . . . . . :   Information
>
>
>
>      - Record Attribute       :
>
>      - Record Claim           : X'40404040404040404040404040404040'
>
>      - Request Claim          : X'00000000000000000000000000000000'
>
>      - Reference Count        : 0
>
>      - Second Context         : *NONE
>
>      - Second Name            : *NONE
>
>      - Alternate Name         : *NONE
>
>      - Second Alternate Name  : *NONE
>
>      - Attribute Library      : *NONE
>
>      - Attribute Name         : *NONE
>
>
>
>
>
>
>
>
> Bottom
>  Press Enter to continue.
>
>
>
>
> Mark Allen
> IS Manager
> Wilkes Telephone & Electric
> 11 W. Court Street
> Washington, GA 30673
> Phone: (706) 678-9565
> Fax: (706) 678-1000
>
>
>
> _______________________________________________
> 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.cgi/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.cgi/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.cgi/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 ...

Follow-Ups:
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.