I believe the original poster mentioned z/VM (CMS). The latest COBOL
compiler for z/VM is COBOL for VM, IBM Program No. 5698-A25. This compiler
is still available for licensing and fully IBM supported.
- - - - - - - - - -
Timothy Sipples
I.T. Architect Executive
Digital Asset & Other Industry
On Fri, 22 Jan 2021 01:06:10 +, CM Poncelet wrote:
>The "END " should always be coded to ensure that the
>beginning of "" is also the entry point.
>
How does this play with SMP/E service which regularly scrambles CSECTs
and doesn't AFAIK generate INCLUDE -ATTR?
Would the programmer more
The "END " should always be coded to ensure that the
beginning of "" is also the entry point.
On 21/01/2021 20:54, Jesse 1 Robinson wrote:
> Without some kind of explicit ENTRY indicator within the source--like END
> BAMKAPP--there was no ENTRY point generated in the app module. Hence
>
On Thu, 21 Jan 2021 20:22:22 +, Jesse 1 Robinson wrote:
>
>Not so fast. We discovered from their install jobs that they had coded
>something like this:
>
> BANKAPP
> Lots of code and calls including the IBM module
> END
>
>As long as the program was compiled and linked in the same run,
Without some kind of explicit ENTRY indicator within the source--like END
BAMKAPP--there was no ENTRY point generated in the app module. Hence specifying
ENTRY BANKAPP to the linker got 'not found'. Maybe today's binder takes care of
this, but in the 80s we could not find an obvious way to
No one knew how to code an ENTRY statement?
Personally, I'd make that message the Binder emits about defaulting the
entry point to be an RC=8 level error. I usually discover this oversight
when something crashes after an APPLY, and by then, it's not so simple to
add the ENTRY.
sas
On Thu, Jan
(I know it's not Friday, but time these days is twisted beyond recognition) I
used to work for a bank. One Monday morning, we were told that we needed to
provide a disaster recovery platform for another bank with whom we had a mutual
support agreement. ASAP. Which was totally news to us.
Thank you Greg, Paul and Max for your informative replies!
On Tue, 5 Jan 2021 at 15:12, Massimo Biancucci wrote:
> I tried to develop you hints:
>
> // EXPORT SYMLIST=*
> // SET INPMOD=oldmd
> // SET OUTMOD=newmod
> // SET INPLIB=myold.lib
> // SET OUTLIB=mynew.lib
> // SET AMBDSN=AMBLIST3
> //
Ah! thank you Ronald, that works
Carmen Vitullo
-Original Message-
From: Ronald
To: IBM-MAIN
Date: Thursday, 21 January 2021 8:12 AM CST
Subject: Re: clarification please - is z/OSMF required for migrating z/OS from
v2.3 to v2.4 ?
Carmen,
If you open the workflow and
Carmen,
If you open the workflow and select 'Actions' > 'Export workflow as Printable
Format', I think, you can accomplish just that. I believe you can even filter
on that specific task.
Ronald Kristel
From: IBM Mainframe Discussion List on behalf of
Carmen
I am about 89 % complete with my install, one thing I wish would be the ability
to copy or export some migration actions I still have to do.
for example, the Remove or delete data sets, paths and references, rather than
having to continue to come back to z/OSMF each time and check what I have
When I don't what to see the member list when I transmit a PDS, I issue the
commands as follows:
xmit dest.userid dsn(/) sysout(z)
output class z is defined as dummy in jes so nothing prints to the output queue.
I use the above command in ISPF 3.4 dsn list; hence, the dsn(/) keyword.
On the
Thanks. I read that doc. It doesn't coexists with VENDOR.C750.LIBCXX.A.
I may create some alias data sets.
On 21/01/2021 8:20 pm, Joe Monk wrote:
according to here:
https://support.sas.com/archive/installation/admindoc/installation/c_7.50F_MVS.pdf
Its prefix.RW.LIBSTD.A and
according to here:
https://support.sas.com/archive/installation/admindoc/installation/c_7.50F_MVS.pdf
Its prefix.RW.LIBSTD.A and prefix.RW.LIBTOOLS.A for the rogue wave libs...
look at page 58/61
Joe
On Thu, Jan 21, 2021 at 4:04 AM David Crayford wrote:
> I'm working on a project that
There are SAS/C devs on this mailing list so I may get lucky!
On 21/01/2021 6:07 pm, Gadi Ben-Avi wrote:
How about asking SAS.
Start at support.sas.com or send a message to supp...@sas.com
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
David Crayford
Sent:
It's not out of support. It's been withdrawn from marketing which is not
the same thing. We're paying for it so I hope somebody is supporting it!
On 21/01/2021 7:51 pm, Robin Atwood wrote:
SAS/C went out of support in about 2004! Good luck getting support.
Robin
-Original Message-
SAS/C went out of support in about 2004! Good luck getting support.
Robin
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Gadi Ben-Avi
> Sent: 21 January 2021 17:07
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: SAS/C++ help
>
> How about asking SAS.
> Start at
How about asking SAS.
Start at support.sas.com or send a message to supp...@sas.com
Gadi
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
David Crayford
Sent: Thursday, January 21, 2021 12:04 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SAS/C++ help
I'm working on a
I'm working on a project that uses SAS/C++ and I'm having problems
getting the sasCC370 compiler in z/OS UNIX configured to include the
Rogue Wave STL library. In the sascc.cfg file I specified
CXXLIBPREFIX=VENDOR.C750.RW
but then it failed because the LIBCXX data set was not found. I tried to
19 matches
Mail list logo
