On 8 Nov 2005 14:47:32 -0800, [EMAIL PROTECTED] (Ray Mullins) wrote:
Try PARM='/DATAHERE'. This has to do with COBOL runtime options. But I can
never remember if user parm data follows or proceeds the slash.
I'm unfamiliar with use of the slash, I've never worked in a site that
used it. What
Howard,
As stated in previous posts on this issue, LE options can be part of the
PARM input. So depending on how your shop has setup LE and COBOL, the LE
parms (if you want to overrides) either comes before the / or after.
CBLOPTS which does determine whether or not the user data should come
One example with which I am aware is the RTEREUS option. IBM recommends:
Avoid using RTEREUS(ON) as an installation default. If you do use RTEREUS,
use it for specific applications only.
At my previous job, we had a financial package from GEAC which (IIRC) had a
main assembler program calling
[mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 09, 2005 9:09 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Passing PARM to COBOL.
On 8 Nov 2005 14:47:32 -0800, [EMAIL PROTECTED] (Ray Mullins) wrote:
Try PARM='/DATAHERE'. This has to do with COBOL runtime options. But I
can never remember if user
Howard Brazee wrote:
On 8 Nov 2005 14:47:32 -0800, [EMAIL PROTECTED] (Ray Mullins) wrote:
Try PARM='/DATAHERE'. This has to do with COBOL runtime options. But I can
never remember if user parm data follows or proceeds the slash.
I'm unfamiliar with use of the slash, I've never worked in a
Hi,
I've done this before but can't get it to work now. I'm trying to pass an
EXEC PARM field to a batch COBOL program. I have the following:
LINKAGE SECTION.
01 LS-PARM.
05 LS-PARM-DATA-LENGTH PIC 9(04) BINARY.
05 LS-PARM-DATA PIC X(100).
PROCEDURE DIVISION USING
Craig,
The hex 40C makes me think you have the length field incorrectly coded.
Should it be a COMP-3 field instead of a BINARY field?
Lizette Koehler
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send
On Tue, 8 Nov 2005 17:35:40 -0500, Craig Kittendorf
[EMAIL PROTECTED] wrote:
Hi,
I've done this before but can't get it to work now. I'm trying to pass an
EXEC PARM field to a batch COBOL program. I have the following:
LINKAGE SECTION.
01 LS-PARM.
05 LS-PARM-DATA-LENGTH PIC 9(04)
PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Passing PARM to COBOL.
Hi,
I've done this before but can't get it to work now. I'm trying to
pass an
EXEC PARM field to a batch COBOL program. I have the following:
LINKAGE SECTION.
01 LS-PARM.
05 LS-PARM-DATA-LENGTH PIC 9(04) BINARY.
05 LS
I always used s9(4) comp not binary.
don't remember what binary does right now
Mike
On 11/8/05, Craig Kittendorf [EMAIL PROTECTED] wrote:
Hi,
I've done this before but can't get it to work now. I'm trying to pass an
EXEC PARM field to a batch COBOL program. I have the following:
LINKAGE
@BAMA.UA.EDU
Subject: Passing PARM to Cobol
Craig,
The hex 40C makes me think you have the length field incorrectly coded.
Should it be a COMP-3 field instead of a BINARY field?
Lizette Koehler
--
For IBM-MAIN subscribe / signoff
PARM='/DATAHERE' will attempt to pass DATAHERE to the LE runtime.
Thanks,
Craig
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Ray Mullins
Sent: Tuesday, November 08, 2005 5:47 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Passing PARM to COBOL
PARM='/JFIPJFIA' would pass JFIPJFIA to the LE runtime.
Thanks,
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Imbriale, Donald (Exchange)
Sent: Tuesday, November 08, 2005 5:49 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Passing PARM
Binary is equivalent to COMP.
Thanks,
Craig
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Mike Bell
Sent: Tuesday, November 08, 2005 5:51 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Passing PARM to COBOL.
I always used s9(4) comp
I *strongly* recommend using COMP-5 - just in case IBM ever allows for LARGE
parms (and this would work with any setting of the TRUNC compiler option).
However, COMP, BINARY, and COMP-5 should all work exactly the same as long
as MVS only allows for a 100 character maximum (and as long as you are
,
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Of Imbriale, Donald (Exchange)
Sent: Tuesday, November 08, 2005 5:49 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Passing PARM to COBOL.
If your LE run-time option CBLOPTS is OFF, then the format
16 matches
Mail list logo
