Topic
  • 4 replies
  • Latest Post - ‏2013-09-20T22:14:00Z by Tony@First Data
Tony@First Data
Tony@First Data
7 Posts

Pinned topic Scanning error with AIF statement

‏2013-09-19T14:31:14Z |

The scanner is giving a RC=8 for programs that use subscripts in an AIF statement. 

Error:  

RC=8 TYPE=CU ASMA092E: Substring expression 1 points past string end; default=null - OPENC

Code:  

XXXXUSER CSECT

         AIF ('&SYSPARM'(1,2) EQ '24').MODEXIT

XXXXUSER AMODE ANY

XXXXUSER RMODE ANY

.MODEXIT ANOP

     

            

  • TonyLlopis
    TonyLlopis
    59 Posts

    Re: Scanning error with AIF statement

    ‏2013-09-19T16:04:08Z  

    RAA is just reporting an error the assembler has found.    ASMA092E is a message issued by the assembler.    I suggest you try to assemble the same program outside of RAA.    If the error does not occur, then I would suspect a difference in the SYSLIBs being used.   Let us know what you find.

  • Tony@First Data
    Tony@First Data
    7 Posts

    Re: Scanning error with AIF statement

    ‏2013-09-19T21:51:37Z  

    I have assembled the program outside of RAA and the program compiles correctly.  I confirmed that the SYSLIB in the JCL that was used to compile the job outside of RAA was the same as the concatenation set assigned to the file for scanning by RAA.

  • TonyLlopis
    TonyLlopis
    59 Posts

    Re: Scanning error with AIF statement

    ‏2013-09-20T01:44:21Z  

    I have assembled the program outside of RAA and the program compiles correctly.  I confirmed that the SYSLIB in the JCL that was used to compile the job outside of RAA was the same as the concatenation set assigned to the file for scanning by RAA.

    I apologize.  I did not pay attention to the actual statement of the error.   When you run your assembly outside of RAA, it must be being passed a SYSPARM(...) in the options string.   RAA does not, so it defaults to null.   

    Can you verify what it is being passed when assembled outside of RAA?  

    I do not think RAA has a way to do so.    The first quest that comes to mind is  how pervasive is the problem.    

    As a test I would run a search in the REXX library looking for ASMA90.   That will tell where assembler is invoked.   I would copy the member to the CONFIG REXX PDS and modify the parm string to include SYSPARM(...).  

     

     

  • Tony@First Data
    Tony@First Data
    7 Posts

    Re: Scanning error with AIF statement

    ‏2013-09-20T22:14:00Z  

    I apologize.  I did not pay attention to the actual statement of the error.   When you run your assembly outside of RAA, it must be being passed a SYSPARM(...) in the options string.   RAA does not, so it defaults to null.   

    Can you verify what it is being passed when assembled outside of RAA?  

    I do not think RAA has a way to do so.    The first quest that comes to mind is  how pervasive is the problem.    

    As a test I would run a search in the REXX library looking for ASMA90.   That will tell where assembler is invoked.   I would copy the member to the CONFIG REXX PDS and modify the parm string to include SYSPARM(...).  

     

     

    We added SYSPARM to the options string and that has corrected the issue.

    Thanks

    Updated on 2013-09-25T21:13:43Z at 2013-09-25T21:13:43Z by Tony@First Data