DB2 being picky about SQR; also getting an error

[Michael Lee <MLee@AGCONSULT.COM>]

Hello all,

Sometimes, when running an SQR on the client, it runs fine, but when
running on the MVS server, it bombs.

The first item that DB2/MVS doesn't like is the [dynamic tablenames]...
has to be translated to \dynamic tablename\

The second item that DB2/MVS doesn't like is one line of code continued on
the second line:
   let $statement = 'Error caused by ' ||
                                    $Errorcode

Does anyone know what else DB2/MVS is picky about?  What about dynamic
columns?  Is that the same case?  Do those have to be translated to
\dynamic column\ as well?

I just ran an SQR on the server and received the following error and am
trying to figure out what is causing the error:

READY
DSN SYSTEM(DB2B)
DSN
RUN PROG(SQR)       PLAN(DBCALLS)      LIB('TSD.SQR.LOAD')
PARMS('DDN:SQRIN DSN/THRDB06 -FDDN:SQROUT -P
-IDSN:HRS.HR601.SQRINC( -TBZ -MDDN:MAXIN')
DSN          ENDED DUE TO ERROR+
SYSTEM ABEND CODE 04E     REASON CODE 00E7000C     PSW 077C10008CEB3048
ASIDS:  HOME = 005F PRIMARY = 00A5 SECONDARY = 00A5

LSCX041 **** ERROR ****
          ABEND occurred in line   1000 of      SQ043(SQ048)    , offset
000338
          Program terminated by operating system.  ABEND code = S04E
          A non-C or system routine was running at the time of ABEND
Calling trace:
     Function           Line         Offset          Context
     SQ043(SQ048)       1000         000338
     SQ030(SQ030)        277         000B3E
     SQ092(SQ142)       1009         000180
     SQ060(SQ060)         95         000460
     SQ060(SQ060)         95         000460
     SQ060(SQ060)         95         000460
     SQ184(GETPID)       495         000C56
       MAIN(MAIN)       1215         0006F4


Any insight on this would be greatly appreciated.

Michael K. Lee
mlee@agconsult.com
Consultant
AG Consulting, an ADP Company
http://www.agconsult.com