About an OPCODE EVAL-CORR

335 pts.
Tags:
Data structures
iSeries
I would like to have sample code on the OPCODE LIKEREC with all its parameters like with *All and *KEY and *INPUT and *OUTPUT. Also, I want to know whether OPCODE EVAL-CORR in iSeries or not  because when I want to transfer data from one DS (Data Structure) to another DS using EVAL-CORR, I'm getting an error and the error is because of this EVAL-CORR OPCODE. It says 'EVAL OPERAND EXPECTS ASSIGNMENT OPERATOR'.

Software/Hardware used:
ISERIES MOCHATN5250

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.

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

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
  • TomLiotta
    The source examples for LIKEREC are easy. Here's what each variation looks like:
         d recDS           ds                  dim( 2 ) qualified
         d  recEDS1                            likerec( CUSREC )
         d  recEDS2                            likerec( CUSREC : *ALL )
         d  recEDS3                            likerec( CUSREC : *INPUT )
         d  recEDS4                            likerec( CUSREC : *OUTPUT )
         d  recEDS5                            likerec( CUSREC : *KEY )
    But the EVAL-CORR message is a little more difficult. There are no such messages exactly as you show, particularly all in UPPER-CASE, and you didn't give any message ID to look up. So it's too difficult to determine what message it is.   Of course, according to the message text that you do show, you are either missing your assignment operator or you're using an incorrect one. But like the lack of a message ID, you also don't show the source that is getting the error. We can't figure out what might be wrong if you don't show us the lines with the problem.   Tom
    125,585 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