This doesn't sound like something that can be "fixed".  What this command
does 
is close down "resources" (such as open files, programs currently not in the 
invocation stack but still active, etc.) from the next higher invocation 
level.  You are destroying the pointer to these objects that is in your PAG
so 
the error message is a correct one.

This may or may not be the same problem as Doc is having.

-----Original Message-----
From:   Walden Leverich [SMTP:walden@techsoftinc.com]
Sent:   Monday, November 17, 1997 6:27 PM
To:     MIDRANGE-L@midrange.com
Subject:        Re: CPF6A13/CPF6A0B

This has happened on the AS/400 since V3R1. (Maybe V2R3) It has nothing to
do with your C program. Some of the AS/400's screens will end with that
error if you perform a RCLRSC *CALLER. I don't know why, but I reported it
to IBM several YEARS ago and I have not seen it fixed yet.

-Walden
-----Original Message-----
From: Ed.Doxtator@ssa.co.uk <Ed.Doxtator@ssa.co.uk>
To: midrange-l@midrange.com <midrange-l@midrange.com>
Date: Friday, November 14, 1997 2:36 PM
Subject: CPF6A13/CPF6A0B


>
>Has anyone had any experience with the error messages CPF6A13, "Application
>xxxxx closed prematurely." and CPF6A0B, "Application handle xxxxx not
>valid."?
>
>This occurs when doing a RCLRSC LVL(*CALLER) OPTION(*NORMAL) after a C
>program has failed.  The program uses shared memory segments and, if it
>terminates abnormally, files may be left open in the IFS.  (This may or may
>not make any difference, but it's the first time I've seen the message, so
>I blame the stuff I don't know much about.  Call me xenophobic, but
>anything new is bad.)
>
>The funny thing is that the CPF6A13 message says:  "Either the application
>9B810002 was closed before the panel could be displayed again or panel
>group QGWCAJOB in library QSYS was   deleted before the panel could be
>displayed again."  HUH?  What gives?  QGWCAJOB is the *PNLGRP object for
>WRKACTJOB.
>
>Any ideas anyone?
>
>Thanks
>
>-Doc
>
>
>+---
>| This is the Midrange System Mailing List!
>| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
>| To unsubscribe from this list send email to MAJORDOMO@midrange.com
>|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
>| Questions should be directed to the list owner/operator:
david@midrange.com
>+---
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


[**SEND TO DEADMAIL**][X]

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


This thread ...


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

This mailing list archive is Copyright 1997-2019 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].