Home > IT Answers > AS/400 > CPF5423 in ISDB debugging service job
DaveInReddick
20 pts.
 CPF5423 in ISDB debugging service job
AS/400 Client Access, Client Access 6.0, Client Access 6.x, iSeries, V5R4M5
when debugging a COBOL service job, I sometimes get CPF5423 in the debugging session.  I am using Client Access Version 6.0 20091022 S.  This has happened with at least 2 versions of Client Access and at least 2 OS releases.  It only happens if I hit the F5 key before the debug source screen reappears.

Job Log:

CPF5423    Escape                  40   23/02/11  20:38:45.381616  QWSPUT       QSYS        4B8C     QWSPUT      QSYS        4B8C                                      Message . . . . :   Not able to transmit to device QPADEV001H.  Session not in                                                     send condition.                                                                                                                Cause . . . . . :   There was an internal system failure. Recovery  . . . :                                                        Close the files and try the request again.  If the problem occurs again,                                                         enter the ANZPRB command to run problem analysis.                                         IXA0020    Information             00   23/02/11  20:38:45.387072  QIXAMON      QPDA        0011     QIXABKP2    QPDA        001E                                      Message . . . . :   Internal Message.                                                       IXA0021    Information             00   23/02/11  20:38:45.387472  QIXAMON      QPDA        0023     QIXAMON2    QPDA        001E                                      Message . . . . :   Exception CPF5423 occurred in program QWSPUT.                                                                Cause . . . . . :   ISDB encountered an exception in the specified program.                

Thanks



Software/Hardware used:
Client Access v 6.0, V5R4M5 L00
ASKED: February 23, 2011  9:51 PM
UPDATED: June 15, 2012  8:47 PM
RELATED QUESTIONS
Answer Wiki:
When I do "Help about" on my emulator, it says: Personal Communications WorkStation Program Version 6.0 for Windows. At the bottom it says 20091022 S. Thanks
Last Wiki Answer Submitted:  February 24, 2011  6:06 pm  by  DaveInReddick   20 pts.
All Answer Wiki Contributors:  DaveInReddick   20 pts.
To see all answers submitted to the Answer Wiki: View Answer History.


RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

 

I am using Client Access Version 6.0 20091022 S.

AFAIK, there is no such release of Client Access. This list shows the IBM i Access releases along with service packs from the past ten years. Here’s a list of Operating System Release information going back almost to the beginning. I suspect that you might be running IBM i Access v7.1, and you’re seeing a release tag from the PComm emulator; but I don’t have a comparable emulator handy to verify.

As for STRISDB, I didn’t know it was even still available if you’re running i v7.1. It probably is, but I haven’t looked at STRISDB for at least 15 years. It only exists in ‘previous release’ libraries on the v7.1 system I’m looking at. I’d suggest that it shouldn’t be used at all after version 4 of OS/400. It hasn’t been enhanced in a long time. It might have numerous troubles with current releases. The last PTFs were back for V5R3.

Can you clarify your environment? Are you using STRISDB for a specific reason rather than using STRDBG or one of the graphical debuggers? It’s possible that this error will never be corrected, or it might be a trivial operational problem.

Tom

TomLiotta
 107,695 pts.
 

I just noticed the Software/Hardware used:… V5R4M5 piece, so that seems sufficient for the OS part. The emulator side is still unclear. If you can clarify, I can probably run some similar tests to see if any info becomes apparent.

Tom

TomLiotta
 107,695 pts.
 

We are having similar issues on V5r4. Was there any resolution found for this problem?

tagsecure
 10 pts.
 

Was there any resolution found for this problem?

If your problem is with STRISDB, the primary resolution begins with “Stop using STRISDB.”

It’s obsolete and has been for many years. It’s deprecated and is simply going to go away even from ‘previous release’ libraries.

Please clarify what your problem is. Also, please provide your iSeries Access version (including Service level.)

Without a clear statement of your problem, including the software you’re using, there is no way to know if any resolution might work.

Tom

TomLiotta
 107,695 pts.