Sorry about the typo. We are running z/OS 1.13 and not 1.3.
However, Mr. Schwab pointed to the Migration Guide for Enterprise COBOL 5.1
wherein I found this bit of info in the Language Environment's runtime support
for different compilers: Enterprise COBOL for z/OS, Version 5.1 requi
Mark,
Note this COBOL V5 PSP Bucket entry:
13/10/28 COBOL Version 5 now uses the SMP/E FIXCAT process to
identify requisite PTF's. See sections 3.2, 4.2 and 6.1.10
of Program Directory for details. Required PTF's are not
included in PSP. See technote
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Mark Yuhas
>
> I have been asked to install Enterprise COBOL 5.1 which went GA in October of
> 2013.
>
> We are currently running z/OS 1.13 with a current RSU Level of 1404. We have
>
Yuhas
<003e4ad82c3a-dmarc-requ...@listserv.ua.edu> wrote:
> I have been asked to install Enterprise COBOL 5.1 which went GA in October of
> 2013.
>
> We are currently running z/OS 1.13 with a current RSU Level of 1404. We have
> Enterprise COBOL 4.2 and the correspondi
I have been asked to install Enterprise COBOL 5.1 which went GA in October of
2013.
We are currently running z/OS 1.13 with a current RSU Level of 1404. We have
Enterprise COBOL 4.2 and the corresponding LE level that came with z/OS 1.3 in
February of 2012.
Correct me if I am wrong, but, I
Robert Wessel writes:
> DECsystem-10 actually. Although that often is considered a mainframe,
> just not an IBM one.
cp/m history
http://en.wikipedia.org/wiki/CP/M#History
prior to developing cp/m (73/74), kildall had worked with cp67/cms at
naval postgraduate school.
cp/m reflects some of bot
Paul Gilmartin wrote:
On Mon, 24 Mar 2014 10:58:28 -0400, John Eells wrote:
All this means is that z/OS V1.12 includes the necessary levels of
utilities (such as SMP/E, IEBCOPY, and the Binder) needed to install
COBOL 5.1. It's not terribly unusual for the "driving system," or
installation pro
W dniu 2014-03-24 18:54, Paul Gilmartin pisze:
On Mon, 24 Mar 2014 10:58:28 -0400, John Eells wrote:
All this means is that z/OS V1.12 includes the necessary levels of
utilities (such as SMP/E, IEBCOPY, and the Binder) needed to install
COBOL 5.1. It's not terribly unusual for the "driving syst
On Mon, 24 Mar 2014 10:58:28 -0400, John Eells wrote:
>
>All this means is that z/OS V1.12 includes the necessary levels of
>utilities (such as SMP/E, IEBCOPY, and the Binder) needed to install
>COBOL 5.1. It's not terribly unusual for the "driving system," or
>installation product level, requirem
John Eells wrote:
It's not terribly unusual for the "driving system," or installation
product level, requirements to be lower than the levels required to
actually *run* a product.
and of course this is the case. Anciently, rather primitive 'starter
systems' were routinely used for SYSGENs and
Tom Ross wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jousma, David
=20
Both of your statements are correct.
Not only that, but you also need PTFs for four LE APARs and three Binder AP=
ARs.
But you can INSTALL COBOL 5.1 on z/OS 1.12 (according to the Prog
W dniu 2014-03-21 17:14, Tom Ross pisze:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jousma, David
=20
Both of your statements are correct.
Not only that, but you also need PTFs for four LE APARs and three Binder AP=
ARs.
But you can INSTALL COBOL 5.1 on z/OS 1.1
>> -Original Message-
>> From: IBM Mainframe Discussion List On Behalf Of Jousma, David
>>=20
>> Both of your statements are correct.
>
>Not only that, but you also need PTFs for four LE APARs and three Binder AP=
>ARs.
>
>But you can INSTALL COBOL 5.1 on z/OS 1.12 (according to the Program
ssage-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lopez, Sharon
Sent: Monday, March 17, 2014 2:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Enterprise Cobol 5.1
Has anyone migrated to Enterprise Cobol 5.1 from earlier enterprise releases?
I guess that I was r
m
Directory). Go figure
-jc-
>
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Lopez, Sharon
> Sent: Monday, March 17, 2014 2:12 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Enterprise Cobo
List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Lopez, Sharon
Sent: Monday, March 17, 2014 2:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Enterprise Cobol 5.1
Has anyone migrated to Enterprise Cobol 5.1 from earlier enterprise
releases? I guess that I was really surprised that it will not run on z/OS
M-MAIN@LISTSERV.UA.EDU
Subject: Enterprise Cobol 5.1
Has anyone migrated to Enterprise Cobol 5.1 from earlier enterprise releases?
I guess that I was really surprised that it will not run on z/OS 1.12 and that
the executables can only reside in a PDSE. Am I understanding this correctly?
Sharon Lop
Both of your statements are correct.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lopez, Sharon
Sent: Monday, March 17, 2014 2:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Enterprise Cobol 5.1
Has anyone migrated to Enterprise
SERV.UA.EDU
> Subject: Enterprise Cobol 5.1
>
> Has anyone migrated to Enterprise Cobol 5.1 from earlier enterprise
releases? I
> guess that I was really surprised that it will not run on z/OS 1.12 and
that the
> executables can only reside in a PDSE. Am I understanding this cor
ering, amendment or viruses or any consequence thereof.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Lopez, Sharon
Sent: Monday, March 17, 2014 2:12 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Enterprise Cobol 5.1
Has anyone migrat
Has anyone migrated to Enterprise Cobol 5.1 from earlier enterprise releases?
I guess that I was really surprised that it will not run on z/OS 1.12 and that
the executables can only reside in a PDSE. Am I understanding this correctly?
Sharon Lopez
z/OS Systems Programmer
N.C. Office of
Hi, List,
In our DEV environment, currently using Enterprise COBOL v4.2, we specify
TEST=(NOHOOK,SEPARATE,EJPD), and the compiler inserts
DEBUGINF= into a non-executable area of the load module.
IOW, it's just a pointer to a separate dataset containing the information
needed by IBM Debug Tool
22 matches
Mail list logo
