QUSRSPLA / QSPCRTSP API problem Release 5.1 to 5.3

0 pts.
Tags:
DataCenter
Development
Programming Languages
RPG
We have an in-house program that is job logging. This program copies one spool file to another as part of our outq monitor / fax / email distibution process. It calls the QUSRSPLA API to get the spool file attributes and then calls the QSPCRTSP API to duplicate the spool file. It blows up and the error message is; Function check. CPF3CF1 unmonitored by XSY402 at statement 41500, instruction x'006F'. The call to program QSPCRTSP ended in error (C G S D F). Does this ring a bell to anybody? What makes this difficult is that the problem is happening on a newly installed iSeries (running release 5.3) while we are on 5.1. This is a company we spun off, have been supporting and now they have a new install using our custom programs. Any insights would be greatly appreciated. Thanks!
ASKED: February 22, 2005  11:57 AM
UPDATED: February 22, 2005  2:22 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

If you look at that API definition in V5R3, you will find that they have added at least one field to the format you are using. I didn’t dig, but SPLA0200 has added a 10 character field at the end of that format. That would push your error code parameter left by 10 characters, making it an invalid length.
Change your code to determine if the program is running on V5R3 or above and pass a different structure.

John Brandt
iStudio400.com
Home of iS/ODBC – MSSQL Access FROM iSeries

Discuss This Question: 1  Reply

 
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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Dantheband
    SOLVED! As it turns out the length of the QUSRSPLA API reciever variable changed between 5.1 and 5.3 (5.2 as well). EXPERT John Brandt clued me in as to where to look. We changed the length of the SPLA0200 format, recompiled and now it works like a charm.
    0 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.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

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

Following