× 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.



I'm sorry, I did not read all the way thru to see what was happening.

You might have an auto reply value that is doing this

use WRKRPYLE  and check the list that is there.
You may not have added it, but someone else might have thought this was a way 
to have it wait until the record was unlocked, and then the update would occur. 
But if someone else was camped on it in interactive and went for a coffee break 
or some combination, it could be awhile.

You also could use Monitor and test for the status of 1218 and do something 
appropriate.
... send a msg, print an exception report, various things.

maybe this was helpful, I hope it was.

There are probably several other ways to go about this.

Definitely check the auto replies though WRKRPYLE  
  ----- Original Message ----- 
  From: Muralidhar Narayana<mailto:Muralidhar_Narayana@xxxxxxxxxxx> 
  To: midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx> 
  Sent: Friday, February 18, 2005 7:51 AM
  Subject: Any work around to prevent auto-reply


  I see the following statement:

                                            HILOEQ

  c ppmkey chain ppmlc  9090 

  90 under LO will auto reply the error. Am I true? 

   

  The error is something below:

  Record 533972 in use by job 094638/NMURALI/QPADEV00D7. 

  ? C 

  Record 533972 in use by job 094638/NMURALI/QPADEV00D7. 

  ? C 

  Unable to allocate a record in file YPXRSF1 

  Function check. RNX1218 unmonitored by YPU00R

  at statement 2100000001, 

  instruction X'0000'. 

  Unable to allocate a record in file YPXRSF1 (R C G D F). 

  ? R 

  I dont see any message-id however.

  is there any work around to prevent this?

  Thanks for your help

  Murali.

   


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