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



This is a multi-part message in MIME format.
--
Hi all,

I have asked this question before but the response that I got did not help
- but thanks anyway.  Maybe a few more details might help to jog someone's
memory.

I have a customer data base which lists all customers in a subfile.  I
select a customer and another subfile appears showing transactions.
Selecting a particular transaction will drop you down another level to see
the records making up that total transaction i.e. another subfile appears.
It only appears briefly and then the program falls over and I get a message
Permanent I/O error occurred in file PR544FM.

If I do a F1 on the message it shows me the details of that message eg.

Message ID . . . . . . :   RNX1251
Date sent  . . . . . . :   11/10/01      Time sent  . . . . . . :
15:37:10
Message . . . . :   Permanent I/O error occurred in file PR544FM.
Cause . . . . . :   RPG procedure PR544 in program PRSLIBPO/PR544 detected
a
  permanent (not recoverable) file, session, or device error. The session,
  device and/or program has been stopped. Examine the major/minor return
code
  value to determine the specific error that occurred. If the major return
  code is 80 then a system or file error occurred and programmer action is
  required to fix the problem. If the major return code is 81 then a
session
  or device error occurred, but use of another session or device may be
  successful.
Recovery  . . . :   Check the job log for more information on the cause of
the
  error and contact the person responsible for program maintenance.
Technical description . . . . . . . . :   The major return code is 80. The
minor return code is C0.

At the bottom of this screen there is an F10=Display Messages in Job Log.

This is what I see.

Library PRSLIBPF added to library list.
Library PRSLIBPO added to library list.
Library RCFPRDDTA already exists in library list.
Library RCFPRDOBJ already exists in library list.
Current library changed to PRSLIBPF.
Library list changed.
Object PRVMNM in QTEMP type *FILE not found.
Object PRVMNM in QTEMP type *FILE created.
1 objects duplicated.
Member PRVMNM file PRVMNM in QTEMP cleared.
Open of member PRDTLL01 was changed to SEQONLY(*NO).
Member PRDTLL01 file PRDTLL01 in PRSLIBPF opened.
Data sent to device ITSI4591 not valid.  Negative response code is
  1005012B.
Permanent I/O error occurred in file PR544FM.
Function check. RNX1251 unmonitored by PR544 at statement 0000000571,
  instruction X'0000'.
Permanent I/O error occurred in file PR544FM (C G D F).
Permanent I/O error occurred in file PR544FM (C G D F).

If I look at the message prior to  the Permanent I/O error it says Data
Sent to device ITSI4591 not valid.  Negative response code is 1005012B.  I
believe this is the problem that is causing the IO error.

 Message ID . . . . . . :   CPF5192
 Date sent  . . . . . . :   11/10/01      Time sent  . . . . . . :
15:37:10
 Message . . . . :   Data sent to device ITSI4591 not valid.  Negative
response
   code is 1005012B.
 Cause . . . . . :   The condition was caused by the program output data
   containing below hex 40 or too many input fields.  More information on
the
   negative response code can be found in either the IBM 5494 Remote
Control
   Unit Functions Reference (under negative responses) or the SNA Formats
   Manual (under SENSE or LUSTAT codes).  Invalid data (below hex 40) may
have
   occurred in one of the following ways:
     Invalid parameter data passed in variable to command language program.
   Variable is used in SNDPGMMSG command.  Command fails when data is
   displayed.
     Hexadecimal characters below hex 40 entered into TEXT parameter of
create   command.  Display command for object fails when object parameters
are
  displayed.
    Data base record containing invalid data displayed by the application
  program.
    Failure to specify RSTDSP(*YES) when alternating displays from more
than
  one file to the device, where both files have input fields.
Recovery  . . . :   Correct the program or the output data.  Try the
command
  again. If the problem occurs again, enter the ANZPRB command to run
problem
  analysis.


I looked up 1005012B in the online IBM library help but do not understand
the explanation given.

"For local display stations, a start-of-header order length greater than 11
causes the negative response hex 1005012B to be sent.  No negative response
is sent for remote display stations."

Can anyone offer any suggestions as to the meaning of this explanation or
perhaps a solution to my problem.

Kylea White
Analyst Programmer

Burswood International Resort Casino
Great Eastern Highway
BURSWOOD   WA   6100
Phn:  61 8 9362 7016
Fax:  61 8 9470 1789
Email:  KWhite@burswood.com.au
Web:  http://www.burswood.com.au





--
****************************************************************************************************************
                                       Privacy and Confidentiality Notice

The information contained herein and any attachment is intended solely for the 
named recipients.
It may contain privileged confidential information. If you are not an intended 
recipient,
please delete the message and any attachments and notify the sender of 
mis-delivery:
Any use or disclosure of the contents of either is unauthorised and may be 
unlawful.
All liability for viruses is excluded to the fullest extent permitted by law.
****************************************************************************************************************



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.