ist On Behalf Of
Frank Swarbrick
Sent: Monday, April 10, 2023 2:25 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed???
Quite odd, I'll say. But at least I have an answer. Thanks!
I wonder why LONGUPPER has the restrictions it does.
ubject: Re: Cobol calling module with non alphanumeric no longer allowed???
Interesting. Apparently it works for both PGMNAME(COMPAT) and
PGMNAME(LONGMIXED), but not for PGMNAME(LONGUPPER), which is what we are using.
19 001600 procedure division.
20 001610 call
exact compile error?
Note that such a program id would need to be enclosed in quotes for that to
compile.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Frank Swarbrick
Sent: Saturday, April 8, 2023 1:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling
GUPPER).
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Schmitt, Michael
Sent: Monday, April 10, 2023 8:31 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed???
A call to '@SEPTEST' compiles for me with both
9, 2023 12:51 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed???
The only CICS routines that MUST be statically linked are the DFH
subroutines that are called as the result of coding CICS commands like EXEC
CICS LINK or EXEC SQ
in quotes for that to
compile.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Frank Swarbrick
Sent: Saturday, April 8, 2023 1:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed???
I am indeed using DYNAM.
I
On Fri, 7 Apr 2023 22:07:03 +, Frank Swarbrick wrote:
>I've tried calling modules (that exist!) with both '@' and '#' signs in them
>and Enterprise COBOL 5+ does not allow this. COBOL 4 allowed this. Is there
>any good reason why this is the case?
>
No. Higher level components should not
some perceived benefit. To each their own.
>
> Peter
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf
> Of Steve Thompson
> Sent: Sunday, April 9, 2023 4:14 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Cobol calling module w
ed benefit. To each their own.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Steve Thompson
Sent: Sunday, April 9, 2023 4:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed???
In the case o
ral CALL's is when you are
using nested subroutine programs in the same source file as the calling program.
Peter
-Original Message-
From: IBM Mainframe Discussion List On
Behalf Of Frank Swarbrick
Sent: Friday, April 7, 2023 6:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Cobol calling m
Of
Steve Thompson
Sent: Sunday, April 9, 2023 2:16 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed???
The other reason for the literal calls is because one wants the load module to
have the subroutines statically linked that the COBOL program
nested subroutine programs in the same source file as the calling program.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Frank Swarbrick
Sent: Friday, April 7, 2023 6:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Cobol calling module with non alphanumeri
urious about.
>
> From: IBM Mainframe Discussion List on behalf
> of Farley, Peter <031df298a9da-dmarc-requ...@listserv.ua.edu>
> Sent: Friday, April 7, 2023 11:50 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Cobol calling module with non alphanumeric no long
:50 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed???
Not true for non-static calls. We are past COBOL 5 (V6.2 at the moment) and
"CALL variable USING . . . " where "variable" has any of the "national"
ch
is when you are
using nested subroutine programs in the same source file as the calling program.
Peter
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Frank Swarbrick
Sent: Friday, April 7, 2023 6:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Cobol calling module with non
Mainframe Discussion List on behalf
> of Charles Hardee
> Sent: Friday, April 7, 2023 4:11 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Cobol calling module with non alphanumeric no longer
> allowed???
>
> Are you doing a call literal or call dataname?
>
> On Friday, Apr
Literal. The compiler flags it as not allowed.
From: IBM Mainframe Discussion List on behalf of
Charles Hardee
Sent: Friday, April 7, 2023 4:11 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Cobol calling module with non alphanumeric no longer allowed
Are you doing a call literal or call dataname?
On Friday, April 7, 2023, Frank Swarbrick
wrote:
> I've tried calling modules (that exist!) with both '@' and '#' signs in
> them and Enterprise COBOL 5+ does not allow this. COBOL 4 allowed this.
> Is there any good reason why this is the case?
>
I've tried calling modules (that exist!) with both '@' and '#' signs in them
and Enterprise COBOL 5+ does not allow this. COBOL 4 allowed this. Is there
any good reason why this is the case?
--
For IBM-MAIN subscribe /
19 matches
Mail list logo
