1 2 Previous Next 18 Replies Latest reply on Mar 18, 2011 7:48 PM by 848222

    Tuxedo Application Runtime for BATCH JES2

    835156
      Hello,

      I have the following problem with the command artjesadmin, with the sample application (JOBA)

      artjesadmin>
      artjesadmin>-i JOBA

      Errors:

      In stderr-
      /export/home/oracle/art11gR1/Batch_RT/ejr/EJR[393]: mt_OptionParse=${MT_OPTION_/export/home/oracle/art11gR1/Batch_RT/ejr/EJR}: bad substitution

      In stdout:

      085514 MessageI (:/export/home/oracle/art11gR1/Batch_RT/ejr/EJR) ERROR: /export/
      home/oracle/art11gR1/Batch_RT/ejr/EJR called by /export/home/oracle/art11gR1/Bat
      ch_RT/ejr/EJR: mi_DisplayFormat identifier(BeginFunction) found but not for func
      tion (/export/home/oracle/art11gR1/Batch_RT/ejr/EJR)
      085514 MessageI (:/export/home/oracle/art11gR1/Batch_RT/ejr/EJR) ERROR: /export/
      home/oracle/art11gR1/Batch_RT/ejr/EJR called by /export/home/oracle/art11gR1/Bat
      ch_RT/ejr/EJR: mi_DisplayFormat identifier(BeginFunction) found but not for func
      tion (/export/home/oracle/art11gR1/Batch_RT/ejr/EJR)
      085514 MessageI (:/export/home/oracle/art11gR1/Batch_RT/ejr/EJR) ERROR: /export/
      home/oracle/art11gR1/Batch_RT/ejr/EJR called by /export/home/oracle/art11gR1/Bat
      ch_RT/ejr/EJR: mi_DisplayFormat identifier(BeginFunction) found but not for func
      tion (/export/home/oracle/art11gR1/Batch_RT/ejr/EJR)

      In ULOG:

      085514.svs420!ARTJESADM.28990.1.-2: ERROR: EJR returns error in input phase, exi
      t code 1, command line EJR -i -j 00000012 -r /export/home/oracle/art11gR1/Batch_
      RT/ejemplos /export/home/oracle/art11gR1/Batch_RT/sample/simpjob/JOBA

      Could you help with this requirement?

      Thanks.
      Greetings
        • 1. Re: Tuxedo Application Runtime for BATCH JES2
          Xin Cao-Oracle
          Hi,

          Could you please try execute the job using EJR to locate whether the error happens in artjesadmin? The command line is
          EJR JOBA
          For this command, any error will be prompt directly. And if the job is executed successfully, the converted script will be in $MT_TMP, the job log will be in $MT_LOG.

          If it still does not work, please check
          1) Environment variable MT_KSH point to ksh88 compliant Korn shell, e.g. PDKSH 5.2.14 or above on Oracle Enterprise Linux 5.4.
          2) The execution permission for files uder <ART_Runtime_Installation>/Batch_RT/ejr directory cannot be changed after installation.

          Regards,
          Xin Cao
          • 2. Re: Tuxedo Application Runtime for BATCH JES2
            835156
            Hi Xin,

            Run the following:

            EJR JOBA

            With the result on screen:

            055002 MessageI (:/export/home/oracle/art11gR1/Batch_RT/ejr/EJR) ERROR: /export/home/oracle/art11gR1/Batch_RT/ejr/EJR called by /export/home/oracle/art11gR1/Batch_RT/ejr/EJR: mi_DisplayFormat identifier(BeginFunction) found but not for function (/export/home/oracle/art11gR1/Batch_RT/ejr/EJR)/export/home/oracle/art11gR1/Batch_RT/ejr/EJR[393]: mt_OptionParse=${MT_OPTION_/export/home/oracle/art11gR1/Batch_RT/ejr/EJR}: bad substitution

            I am using Unix OS SPARC 64 Solaris 10.
            MT_KSH environment variable has the following value:
            /bin/ksh

            greetings.

            Carlos Hernández O.

            Edited by: user13525165 on 7/03/2011 10:02 AM
            • 3. Re: Tuxedo Application Runtime for BATCH JES2
              Xin Cao-Oracle
              Carlos,

              On Solaris 10 Sparc 64-bit, please download pdksh 5.2.14 from http://web.cs.mun.ca/~michael/pdksh/, and build it, then use environment variable MT_KSH to point to this generated "ksh". That should solve your problem.

              Regards,
              Xin Cao
              • 4. Re: Tuxedo Application Runtime for BATCH JES2
                835156
                Hi Xin,

                Thank you very much with this installation because the problem was solved.
                NOTE: This should be in the manual.

                Another question, we have a problem with runtime also Cics-Tuxedo.

                My problem is:
                In the tool to run a Rehosting art11gR1
                program cobol / cics brings Example 3
                (/ Art11gR1/Cics_RT/sample/sample_03/CICS) command
                CICS sets the following error XCTL

                The instruction is executed following

                CALL "KIX__XCTL" USING KIX - KIX INDICS - ALL-ARGS

                error code: 114, pc = 0, call = 1, seg = 0 114 Attempt to
                Beyond access item bounds of memory (Signal 11)

                I have no idea that this is the situation.

                Greetings.
                • 5. Re: Tuxedo Application Runtime for BATCH JES2
                  Xin Cao-Oracle
                  Carlos,

                  For ART Batch Runtime, the required Korn Shell version is described at http://download.oracle.com/docs/cd/E18050_01/artrt/docs11gr1/rtinst/pdsapp_A.html.

                  The ART CICS sample error is reported by Cobol Runtime when loading or executing the Cobol program (.gnt). Does this problem happen on Solaris 10 Sparc 64-bit as well? Are you using Micro Focus Cobol 5.1 64-bit for both compilation and runtime environment? Could you please describe steps through 3270 terminal to reproduce the problem?

                  Regards,
                  Xin Cao
                  • 6. Re: Tuxedo Application Runtime for BATCH JES2
                    835156
                    Hi Xin,

                    Is the demo that has ART CICS, the transaction presents SB00 well the first screen but when you choose any other option to call another transaction sends the error.

                    CICS command that comes before precompilation is:

                    * Transfer control to next program
                    * {normalize-exec-xx 1.3
                           * EXEC CICS
                           * XCTL PROGRAM (PGM-DEST)
                           * COMMAREA (COMM-RECORD)
                           * LENGTH (COMM-LENGTH OF RECORD)
                           * END-EXEC.
                           *--
                                EXEC CICS XCTL PROGRAM (PGM-DEST)
                                          COMMAREA (COMM-RECORD)
                                          LENGTH (COMM-LENGTH OF RECORD)
                                END-EXEC.
                           *}

                    After pre-compilation is:

                    8596* Transfer control to next program
                    8597*{ normalize-exec-xx 1.3
                    8598* EXEC CICS
                    8599* XCTL PROGRAM(PGM-DEST)
                    8600* COMMAREA(COMM-RECORD)
                    8601* LENGTH(LENGTH OF COMM-RECORD)
                    ^L^M* Micro Focus Server Express V5.0 revision 000 10-Mar-11 06:03 Page
                    150
                    * ./RSSBT000.CBL
                    8602* END-EXEC.
                    8603*--
                    8604* EXEC CICS XCTL PROGRAM(PGM-DEST)
                    8605* COMMAREA(COMM-RECORD)
                    8606* LENGTH(LENGTH OF COMM-RECORD)
                    8607* END-EXEC.
                    8608 INITIALIZE KIX--INDICS
                    8609 MOVE LOW-VALUE TO KIX--ALL-ARGS
                    8610 ADD 1 TO KIX--ARGS-NB
                    8611 SET KIX--INDIC-LENGTH(KIX--ARGS-NB) TO TRUE
                    8612 MOVE LENGTH OF COMM-RECORD TO KIX--LENGTH
                    8613 OF KIX--PROGRAM-CTRL-ARGS
                    8614 ADD 1 TO KIX--ARGS-NB
                    8615 SET KIX--INDIC-COMMAREA(KIX--ARGS-NB) TO TRUE
                    8616 SET KIX--COMMAREA-PTR OF KIX--PROGRAM-CTRL-ARGS
                    8617 TO ADDRESS OF COMM-RECORD
                    8618 MOVE LENGTH OF COMM-RECORD TO KIX--COMMAREA-LGT
                    8619 OF KIX--PROGRAM-CTRL-ARGS
                    8620 ADD 1 TO KIX--ARGS-NB
                    8621 SET KIX--INDIC-PROGRAM(KIX--ARGS-NB) TO TRUE
                    8622 MOVE PGM-DEST TO KIX--PROGRAM OF KIX--PROGRAM-CTRL-ARGS
                    8623 CALL "KIX__XCTL" USING KIX--INDICS KIX--ALL-ARGS
                    8624 IF EIBRESP NOT = ZERO
                    8625 PERFORM KIX--HANDLE-CONDITION
                    8626 THRU KIX--HANDLE-CONDITION-END
                    8627 END-IF.
                    8628*}

                    I mention that so you could run the entire CICS demo I had to do the following:

                    * Transfer control to next program
                    *{ normalize-exec-xx 1.3
                    * EXEC CICS
                    * XCTL PROGRAM(PGM-DEST)
                    * COMMAREA(COMM-RECORD)
                    * LENGTH(LENGTH OF COMM-RECORD)
                    * END-EXEC.
                    *--
                    SVSCHO* EXEC CICS XCTL PROGRAM(PGM-DEST)
                    SVSCHO EXEC CICS LINK PROGRAM(PGM-DEST)
                    COMMAREA(COMM-RECORD)
                    LENGTH(LENGTH OF COMM-RECORD)
                    END-EXEC.
                    SVSCHO GOBACK.
                    *}

                    But not the best solution to this.

                    -----------------------------------------------------------------------------------------------------------------------------------------

                    We also commented that even I have problems with JES2 Batch.

                    And submit the jobs but apparently not by replacing the variable $ CURRENT_LABEL.

                    Run out the job JOBA:
                    JOBA EJR

                    Send the following.


                    /export/home/oracle/art11gR1/Batch_RT/sample/simpjob >EJR JOBA
                    /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobBegin: function: not found
                    /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobBegin: syntax error at line 12:
                    (' unexpected
                    /export/home/oracle/art11gR1/Batch_RT/ejr/m_PhaseBegin: function: not found
                    /export/home/oracle/art11gR1/Batch_RT/ejr/m_PhaseBegin: syntax error at line 8:
                    `(' unexpected
                    /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobEnd: function: not found
                    /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobEnd: syntax error at line 6: `('
                    unexpected
                    /export/home/oracle/art11gR1/Batch_RT/sample/simpjob >

                    Greetings.
                    • 7. Re: Tuxedo Application Runtime for BATCH JES2
                      835156
                      We also commented that even I have problems with JES2 Batch.
                      • 8. Re: Tuxedo Application Runtime for BATCH JES2
                        Xin Cao-Oracle
                        Carlos,

                        You've digged so deeply:) Regarding the CICS issue, I noticed you are using "Micro Focus Server Express V5.0". But from http://download.oracle.com/docs/cd/E18050_01/artrt/docs11gr1/rtinst/pdsapp_A.html, only "MicroFocus COBOL 5.1" is supported by ART Runtime. Please use version 5.1 instead of 5.0. And if the problem still exists, please let me know the OS information.

                        For the Batch issue, you mentioned the problem was solved. Does the issue this time happen on a different platform? Are you using PDKSH 5.2.14? And please make sure the execution permission for files uder <ART_Runtime_Installation>/Batch_RT/ejr directory not changed after installation.

                        Regards,
                        Xin Cao
                        • 9. Re: Tuxedo Application Runtime for BATCH JES2
                          835156
                          Hi Xin,

                          Ok, The above problem was solved.
                          Now the problem is that when running the job, ends FAIL me and began to analyze the internal environment variable of job ${CURRENT_LABEL} is not being replaced with the corresponding value.

                          Regards.
                          • 10. Re: Tuxedo Application Runtime for BATCH JES2
                            Xin Cao-Oracle
                            Carlos,

                            ${CURRENT_LABEL} is not taken from enviroment variable. It is determined as following,
                            1) When a job starts execution, ${CURRENT_LABEL} is specified by the "-s" option of the job card.
                            For example, for
                            "m_JobBegin -j JOBA -c A -s START -v 2.0 -p 5"
                            ${CURRENT_LABEL} is "START" when the job is submitted.
                            2) After each step, ${CURRENT_LABEL} is specified by ${JUMP_LABEL}.
                            For example, for
                            "(START)
                            JUMP_LABEL=STEP1
                            echo start
                            ;;
                            "
                            ${CURRENT_LABEL} will be set to "STEP1" after step "START" is done.

                            Regards,
                            Xin Cao
                            • 11. Re: Tuxedo Application Runtime for BATCH JES2
                              835156
                              Xin,

                              Ok, this tells me so that I understand.
                              Job echo in the implementation is as follows:

                              m_JobBegin -j JOBA -c A -s START -v 2.0 -p 5

                              And it always goes straight to step:

                              (*)
                              echo MT_RC
                              MT_RC = S999
                              break
                              ;;

                              FAIL ending.

                              In The Log displays the following, submit the job with artjesadmin:

                              while in
                              label is
                              MT_RC
                              hello, That is in JOBA

                              And is supposed to deploy the following, this does not:

                              while in
                              label is START
                              start
                              while in
                              label is STEP1
                              step1
                              while in
                              label is ENDJOB
                              end
                              hello, That is in JOBA

                              For this reason, when analyzing this variable $CURRENT_LABEL not being replaced as it should be with these tools.

                              If I run it as follows:

                              JOBA EJR, send the following:

                              /export/home/oracle/art11gR1/Batch_RT/sample/simpjob >EJR JOBA
                              /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobBegin: function: not found
                              /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobBegin: syntax error at line 12: `
                              (' unexpected
                              /export/home/oracle/art11gR1/Batch_RT/ejr/m_PhaseBegin: function: not found
                              /export/home/oracle/art11gR1/Batch_RT/ejr/m_PhaseBegin: syntax error at line 8:
                              `(' unexpected
                              /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobEnd: function: not found
                              /export/home/oracle/art11gR1/Batch_RT/ejr/m_JobEnd: syntax error at line 6: `('
                              unexpected
                              /export/home/oracle/art11gR1/Batch_RT/sample/simpjob >

                              I would appreciate you helping me with this.



                              Regards,
                              Carlos Hdez.
                              • 12. Re: Tuxedo Application Runtime for BATCH JES2
                                Xin Cao-Oracle
                                Carlos,

                                The error for "EJR JOBA" should be caused by incompatible Korn shell. Please use PDKSH 5.2.14, and set environment variable MT_KSH to point to this PDKSH. If the problem still exists, please let me know the platform you are using.

                                The log I got for the sample "JOBA" is as following,

                                $ cat JESROOT/00000008/LOG/00000008.log
                                JOB JOBA BEGIN AT 2011/03/15 00:38:24
                                in while
                                BEGIN PHASE START AT 2011/03/15 00:38:24
                                label is START
                                start
                                (ACC): resources release
                                END PHASE START AT 2011/03/15 00:38:24 (RC=C0000, JOBRC=C0000, ELAPSED=0)
                                in while
                                BEGIN PHASE STEP1 AT 2011/03/15 00:38:24
                                label is STEP1
                                step1
                                (ACC): resources release
                                END PHASE STEP1 AT 2011/03/15 00:38:24 (RC=C0000, JOBRC=C0000, ELAPSED=0)
                                in while
                                BEGIN PHASE ENDJOB AT 2011/03/15 00:38:24
                                label is ENDJOB
                                end
                                hello, that is in JOBA
                                (ACC): resources release
                                END PHASE ENDJOB AT 2011/03/15 00:38:24 (RC=C0000, JOBRC=C0000, ELAPSED=0)


                                JOB ENDED WITH CODE (C0000) AT 2011/03/15 00:38:24

                                Regards,
                                Xin Cao

                                Edited by: Xin Cao on 2011-3-14 上午9:39
                                • 13. Re: Tuxedo Application Runtime for BATCH JES2
                                  835156
                                  Xin,

                                  The environment variable is pointing to MT_KSH to pdksh 5.2.14, which recently installed thanks to your help.
                                  The operating system you're using is SunOS 10 SPARC 64-bit.

                                  Greetings.
                                  Carlos Hdez.
                                  • 14. Re: Tuxedo Application Runtime for BATCH JES2
                                    Xin Cao-Oracle
                                    Carlos,

                                    If it is not the PDKSH problem, then it should be the wrong execution permission for ART Batch Runtime. The execution permission for files uder <ART_Runtime_Installation>/Batch_RT/ejr directory cannot be changed after installation.

                                    For example, the correct file permission is
                                    $ ls -l art11gR1PS2/Batch_RT/ejr/m_JobBegin
                                    -rw-r----- 1 xcao units 5740 Mar 15 10:17 art11gR1PS2/Batch_RT/ejr/m_JobBegin

                                    It should not be
                                    $ ls -l art11gR1PS2/Batch_RT/ejr/m_JobBegin
                                    -rwxr-x--x 1 xcao units 5740 Jul 21 2010 art11gR1PS2/Batch_RT/ejr/m_JobBegin

                                    Please re-install ART Runtime, and do not use "chmod" to grant permissions for this installation. You may use "chown".

                                    Regards,
                                    Xin Cao
                                    1 2 Previous Next