Re: Parameter integrity error occurred with reason code 3

Thank you.
I changed the option template parameter *NOCLRPSSA of the QPRCRTPG API to 
*CLRPSSA and it's put the axe in the helve!

With p.1,3 the result is equally unsuccessful.

But I don't understand p.2. 
If the truth I open SOMEPF, read, write data on the SOMEDSPF and close SOMEPF 
and then open and close a lot of others files in the program.
The main aim for OPEN/CLOSE is to avoid locks.
You mean I can not to close SOMEPF before the program ends, but in this case i 
need to unlock the file after update (for ex.) and then lock it.
What should i do in this case?

Your UFCB is in static storage, but your program never deactivates the
UFCB.

I suggest one of three solutions:

(1) Change your UFCB to be in automatic storage.

(2) Do have your UFCB in static storage; however, do not call the SEPT
program to close the file before the program ends.

(3) Do have your UFCB in static storage, and do close the file; however,
code a DEACTPG * before your PEND.

A personal observation:

Your UFCB has gaps with no explicit initial value.  IMHO that may create a
bug because you must trust that the program will not be compiled with
*NOCLRPSSA and/or *NOCLRPASA in the option template parameter of the
QPRCRTPG API.

_______________________________________________
This is the MI Programming on the AS400 / iSeries (MI400) mailing list
To post a message email: MI400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/mi400
or email: MI400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/mi400.