Session or Device error

2550 pts.
Tags:
AS/400
AS/400 Subfiles
Any ideas on how this might occur ? Even a hunch would help. A remote user recently got this error. So far, I've been unable to make it happen. I believe I've only seen this when doing MANY pagedown requests (so subfile exceeds the 4-digit RRN field). This application gets maybe 50 subfile records ... far short of the 9,999 max.


Software/Hardware used:
as400
0

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

Discuss This Question: 8  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.
  • philpl1jb

    Well if it's related to subfiles.

    1. It could be the number of the RRN -- it cannot exceed 9999

    2. If using the SFLRCNBR display keyword the value cannot be zero or exceed the current size of the subfile.

     

    54,090 pointsBadges:
    report
  • TheRealRaven
    Very difficult to guess because there are many possibilities. And nowadays almost all users are 'remote' users from the system's viewpoint. A lot more detail could help.

    Was it a "one time" problem? Is it a subfile? What was the user doing -- actively working a screen or was it after a break or other?
    36,035 pointsBadges:
    report
  • aceofdelts

    Phil - thanks ... I'll try tracing (in the program) all changes to the RRN values.

    Raven - I'm told this happened multiple times. Multiple users (concurrently). A fairly simple subfile. They say it was when processing multiple lines (reporting movement of Lots) the neither me nor the B/A were able to replicate. I'll try it again with multiple sessions going.


    Thanks for the ideas. 

    2,550 pointsBadges:
    report
  • TheRealRaven
    Multiple users -- were other users unaffected while doing unrelated tasks on the same server? If so, then network interruptions can possibly be eliminated. Is it happening on multiple days?
    36,035 pointsBadges:
    report
  • philpl1jb

    Multiple users accessing the same set of records with update access?

    The cascade of problems might be started by a locked record.

    54,090 pointsBadges:
    report
  • ToddN2000
    Can you post more of the error details from the job log of the user? Is there a CPF or other error code? It might be some bad data that cannot be displayed.
    134,720 pointsBadges:
    report
  • aceofdelts

    Thanks again for all these ideas !

    An underlying problem here is the info I got is sketchy and this group of users has a track record of exaggerating. They did take a screen image of the error text - came from CPF5140 (per joblog).

    I want to write this off as "they are clicking the red X", but the ability to print that screen error implies an actual session halt.

    No data decimal error for screen info - all is converted to alpha before the screen is rendered. Not sure if any other type of bad data could occur.

    I tried it while having a soft lock (handled via a work file) on one of the Lots ... the "move" request blew through this and did the move anyway (kinda bad but not the issue I'm chasing right now). I'll try a test script with a hard lock, tho I expect to get something other than a device error.

    It's normal here to allow multi-users changing the same data at the same time. The programs expect this and allow for it (e.g., same Lot move reporting by another session would get an error message that the Lot info has changed since the last screen update. I'd try a concurrent run but the darn thing is so fast that I can't.

    Users claimed they got this error "all the time" so you'd think I'd have more info. I think they do click the red X because every joblog ends with the device error below - I guess there'd be no joblog for a normal session end. But too many of these joblogs is bad because it means mis-information.

    Joblogs end with ...

    Message . . . . : Session stopped by a request from device QPADEV00TK. Cause . . . . . : The request shutdown was caused by either the user turning the power off, by a device error, or the ASCII controller inactivity timer expired. Recovery . . . : Close the files and vary the device off (VRYCFG command). If the problem occurs again, enter the ANZPRB command to run problem analysis.

    2,550 pointsBadges:
    report
  • rajeshkmr571
    If there is no data on your subfile and on that time if you turn on sfldsp then that session or device error will occur. you need to check RRN. In other case if you change(add/remove) the display file field attributes then you must recompile the display file otherwise this error will occur
    220 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

Thanks! We'll email you when relevant content is added and updated.

Following

Share this item with your network: