Operation squence not valid & running out of indicators.

[satya]

I have a scenario here. Where i have to do a validation on 6 similar fields and turn up Reverse image whenever there are errors.I am running out of indicators .Can anyone pls suggest me some other way of doing these.I have to do the same for different set of fields too.



There is another scenario where i am trying to update the file.and it gives me an error saying

Operation sequence not valid for member.

I am trying to validate the data using a chain operation to see if the record exists before doing the above operation.

If i am not doing the chain the update works fine.however after he chain it says the error.

Anyway out of this.?

[DeadManWalks]

Re: Operation squence not valid & running out of indicators.

code please.

[satya]

Re: Operation squence not valid & running out of indicators.

code please.

Cannot post the code.Since i am not alllowed to do.Do you require the error description code.Please let me know wht els i can help you with.

[tomliotta]

Re: Operation squence not valid & running out of indicators.

Simple answer might be "Don't use indicators." Why are you using them? Use &program-to-system fields and set the attributes with DSPATR(&program-to-system).

[jamief]

Re: Operation squence not valid & running out of indicators.

create an indicator array -- there are some examples on the site.
then save the indicators prior to the *NEW section you are using.
then reuse an indicator and when you leave the new section..
Put the indicators back to what they were before you started.

This would be difficult to follow and not recommended, but put a bunch
of documentation around the code so others wont get AS lost.

Jamie

[GLS400]

Re: Operation squence not valid & running out of indicators.

I'm with tom here....p-field is the way to go:

http://www.itjungle.com/fhg/fhg101304-story01.html

Best of Luck
GLS

[satya]

Re: Operation squence not valid & running out of indicators.

thanks but i need position cursor also.guess i hv to go jamie's way Jamie if u could kindly post a small code snippet tht would be helpful.Inever used an indicator array as well not able to understand you.

[DeadManWalks]

Re: Operation squence not valid & running out of indicators.

Step 1

     A                                      INDARA

Step 2

     FGl800Fm   CF   E             WORKSTN InDds(Indicators)

Step 3

     d Indicators      ds
     d  InExit                 1      1n
     d  InSearch               3      3n
     d  InUpdate               7      7n
     d  ErrorFromYear...
     d                        30     30n
     d  ErrorStore            31     31n
     d  ErrorFromPer          32     32n
     d  ErrorToYear           33     33n
     d  ErrorToPer            34     34n

     d  Error_From_Major...
     d                        35     35n
     d  Error_From_Minor...
     d                        36     36n
     d  Error_To_Major...
     d                        37     37n
     d  Error_To_Minor...
     d                        38     38n

[DAG0000]

Re: Operation squence not valid & running out of indicators.

thanks but i need position cursor also.guess i hv to go jamie's way Jamie if u could kindly post a small code snippet tht would be helpful.Inever used an indicator array as well not able to understand you.

You can use the QUSLFLD (List Field) api to locate the field positions on your display format. Once you have that you can set your cursor location and eliminate the position cursor indicators.

[tomliotta]

Re: Operation squence not valid & running out of indicators.

With only six fields, it's hard to guess how there could be a problem with "running out of indicators". But even for PC, indicators aren't needed. Use the CSRLOC() record-level keyword to position the cursor.

[RayGilliesJones]

Re: Operation squence not valid & running out of indicators.

At a guess, you'd need only two indicators per field (one for PC and RI) and maybe one for PR (assuming that they couldn't share the PR indicator, which they usually can). So that would be 12 indicators at most...?

As for your CHAIN problem, again Im guessing, but how about - you are using READ or CHAIN to pick up the record, some user input maybe, you are CHAINing again to find if the new record exists, (it doesn't), so you issue an UPDATE and it fails... ? If thats the case, your mistake is CHAINing to find the new record - don't do that!