Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.
Solved
How to use "Exception handling *PSSR"
Posted on 2004-09-16
I using RPG IV, and the OS/400 is V4R3 and the RPGLE is V4R2.
I have a program which uses a logical file XOLDCD. The program encounters
the following problem. It is not able to allocate the file XOLDCD because
it is used exclusively by another process.
The error messages are:
Message Data . . . . . . . . . . . . . :
Error message CPF4128 appeared during OPEN for file XOLDCD.
Message Identifier . . . . . . . . . . : CPF4128
Not able to allocate objects needed for file in library
member
According to my knowledge, RPG IV does offers Error handling *PSSR.
However, it does not seem to work. The following are sample of statements
in my program:
HDEBUG(*YES)
F
...
FXOLDCD IF E K DISK
D
...
...
D PSDS SDS
D Procedure *PROC
D Status *STATUS
C
...
...
C *PSSR BEGSR
C Status IFGT 99
C .....
C DUMP
c ROLBK
C .....
C RETURN
C ENDIF
C ENDSR
...
I do not wish to allocate the file in the CL before calling this program,
because it will involve to much changes to my system. I hope someone can
advice me how it can be achieve without using a CL
I have a program which uses a logical file XOLDCD. The program encounters
the following problem. It is not able to allocate the file XOLDCD because
it is used exclusively by another process.
The error messages are:
Message Data . . . . . . . . . . . . . :
Error message CPF4128 appeared during OPEN for file XOLDCD.
Message Identifier . . . . . . . . . . : CPF4128
Not able to allocate objects needed for file in library
member
According to my knowledge, RPG IV does offers Error handling *PSSR.
However, it does not seem to work. The following are sample of statements
in my program:
HDEBUG(*YES)
F
...
FXOLDCD IF E K DISK
D
...
...
D PSDS SDS
D Procedure *PROC
D Status *STATUS
C
...
...
C *PSSR BEGSR
C Status IFGT 99
C .....
C DUMP
c ROLBK
C .....
C RETURN
C ENDIF
C ENDSR
...
I do not wish to allocate the file in the CL before calling this program,
because it will involve to much changes to my system. I hope someone can
advice me how it can be achieve without using a CL
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
5
4- +1
14 Comments
Active 5 days ago
bpteo:
Though you've coded a *PSSR, I don't see a INFSR(*PSSR) coded for the F-spec. I also suggest you code an INFDS for this file so the file status is available to the *PSSR.
(BTW, does this program also have a display file?)
Tom
Though you've coded a *PSSR, I don't see a INFSR(*PSSR) coded for the F-spec. I also suggest you code an INFDS for this file so the file status is available to the *PSSR.
(BTW, does this program also have a display file?)
Tom
Hi,
Thank you for your reply. I have actually tried what you suggested. The following are the codes. But, the program still abend and went into a message wait status. And the dump show that it has not even gone beyond the first statement in the c-specs, not to mention calling the *PSSR subroutine. Any idea why the program does not seem to invoke the exception handling routine *PSSR
HDEBUG(*YES)
F
...
FXOLDCD IF E K DISK INFDS(FileSDS)
F INFSR(*PSSR)
D PSDS SDS
D Procedure *PROC
D Status *STATUS
D
D FileSDS DS
D FileName *FILE
D FileStatus *STATUS
D
C* Start of C specs
C
...
...
C *PSSR BEGSR
C Status IFGT 99
C .....
C DUMP
c ROLBK
C .....
C RETURN
C ENDIF
C ENDSR
...
Thank you for your reply. I have actually tried what you suggested. The following are the codes. But, the program still abend and went into a message wait status. And the dump show that it has not even gone beyond the first statement in the c-specs, not to mention calling the *PSSR subroutine. Any idea why the program does not seem to invoke the exception handling routine *PSSR
HDEBUG(*YES)
F
...
FXOLDCD IF E K DISK INFDS(FileSDS)
F INFSR(*PSSR)
D PSDS SDS
D Procedure *PROC
D Status *STATUS
D
D FileSDS DS
D FileName *FILE
D FileStatus *STATUS
D
C* Start of C specs
C
...
...
C *PSSR BEGSR
C Status IFGT 99
C .....
C DUMP
c ROLBK
C .....
C RETURN
C ENDIF
C ENDSR
...
Hi
a CPF4128 error is issued before your program has even completed in *INZSR prrocess so it will never get to the point of *PSSR.
The way I check for this error is to change the file to user open in the RPG and check for the error during the open.
dave
a CPF4128 error is issued before your program has even completed in *INZSR prrocess so it will never get to the point of *PSSR.
The way I check for this error is to change the file to user open in the RPG and check for the error during the open.
dave
Active 5 days ago
(D'oh!) Dave's right. If you want to move allocation testing and response into the RPG program and out of the control language, then the program must take full control.
I tend to use control language (CL) for such control functions and put business logic into business programs, so it's been far too many years since I've seen CPF4128 actually occur within RPG.
Tom
I tend to use control language (CL) for such control functions and put business logic into business programs, so it's been far too many years since I've seen CPF4128 actually occur within RPG.
Tom
Hi again
You can not even check for this on a monmsg! Aghhhhhhhhhh
It's all about what part of the system you want to change.
The cleanest way is in the CL, so the program won't dump and you can easily send a mesasge to who ever to tell them about the problem.
Dave
You can not even check for this on a monmsg! Aghhhhhhhhhh
It's all about what part of the system you want to change.
The cleanest way is in the CL, so the program won't dump and you can easily send a mesasge to who ever to tell them about the problem.
Dave
Active 5 days ago
Dave:
I assume you mean a MONMSG against the CALL to the RPG program fails rather than against an ALCOBJ prior to the CALL?
Tom
I assume you mean a MONMSG against the CALL to the RPG program fails rather than against an ALCOBJ prior to the CALL?
Tom
Hi
just a thought, if it is only the one logical file that is the problem; why not just duplicate it to a new name in the same library, the system will share the access path so they will be no system overhead. Change the one program that has an exclusive lock to use the new logical enabling all the other programs to function correctly.
Dave
just a thought, if it is only the one logical file that is the problem; why not just duplicate it to a new name in the same library, the system will share the access path so they will be no system overhead. Change the one program that has an exclusive lock to use the new logical enabling all the other programs to function correctly.
Dave
Active 5 days ago
Dave:
If it's a lock against the object, that should work. But if it's a lock based on the data member (i.e., the underlying physical), then I'd expect to see the same problem. No?
Seems to me that USROPN combined with explicit allocation is still the best course. Or ALCOBJ prior to CALLing the RPG. And make sure that the correct object is allocated with the appropriate lock.
Tom
If it's a lock against the object, that should work. But if it's a lock based on the data member (i.e., the underlying physical), then I'd expect to see the same problem. No?
Seems to me that USROPN combined with explicit allocation is still the best course. Or ALCOBJ prior to CALLing the RPG. And make sure that the correct object is allocated with the appropriate lock.
Tom
Hi tom
I am unsure how the object is locked. Depending on how it is locked it could work.
Please can you tell us how the object is locked.
I am unsure how the object is locked. Depending on how it is locked it could work.
Please can you tell us how the object is locked.
I believe the problem is the file lock situation and handling it in RPG is easier. You can keep infsr with delay wait for certain time. and respond to the job as 'R' after some time...but this is not the right way
The other way out is you can figure out which job is locking from the sds around 90 to 118 in the ds will have the information
You can send a msg to qsysopr once the lock is released there by taking R would help.
The other way out is you can figure out which job is locking from the sds around 90 to 118 in the ds will have the information
You can send a msg to qsysopr once the lock is released there by taking R would help.
Featured Post
The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Check out what's been happening in the Experts Exchange community.
- Acronis
- Belatrix Software
- Webroot
- Ransomware
- Experts Exchange
- Targus, Security
In this article, I’ll show how research, determination, and use of modern technology helped me solve a DNA mystery.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Want to learn how to record your desktop screen without having to use an outside camera. Click on this video and learn how to use the cool google extension called "Screencastify"!
Step 1: Open a new google tab
Step 2: Go to the left hand upper corn…
Suggested Courses
Course of the Month9 days, 1 hour left to enroll
721 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.