The main reason of STP is to coordinate time between the CECs. When you have
only one, there is nothing to coordinate anymore.
Kees.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Mark Jacobs - Listserv
Sent: 19 January, 2016 21:06
On Jan 19, 2016, at 8:11 PM, Dale R. Smith wrote:
On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills
wrote:
"(c) International Business Machines Corporation 1974, 1976, 1981"
35 to 42 years old!
Charles
The last supported release of the OS/VS COBOL Compiler and Library
was V1.2.4. It
It does not ship with z/OS. It is withdrawn from marketing, my understanding of
which is "you can't order it."
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Dale R. Smith
Sent: Tuesday, January 19, 2016 6:12 PM
To: IBM-MAIN
On Tue, 19 Jan 2016 12:33:44 -0800, Charles Mills wrote:
>"(c) International Business Machines Corporation 1974, 1976, 1981"
>
>35 to 42 years old!
>
>Charles
The last supported release of the OS/VS COBOL Compiler and Library was V1.2.4.
It was withdrawn from marketing in June 1992 and withdra
It's common practice for us to have at least two service levels in play at the
same time. One for the 'next big thing' and one for 'keep the lights on' in the
current production release. Having distinct static service environments means
that nothing gets in anyone else's way. Either can be clone
I vote for Bruce's method also. This will allow multiple versions (a
maintenance version of current and the next Version release) to be mounted at
the same time. Allows two people or parallel work on both systems.
I even went so far as to write a REXX routine which would create the mount
poin
"(c) International Business Machines Corporation 1974, 1976, 1981"
35 to 42 years old!
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Pinnacle
Sent: Tuesday, January 19, 2016 12:14 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re
I had the same question. Like maybe the JCL containing the ancient compiler
name was pulled from the same archive as the source. But others have pointed
out that hex literals were not allowed in the OS/VS compiler, so this
particular combination of source and JCL could never have worked.
.
.
.
On 1/19/2016 1:58 PM, Ron Thomas wrote:
I looked at the endevor processor group setting and it is showing the program
that is used is PGM=IKFCBL00. is this won't work ? Thanks!
--
For IBM-MAIN subscribe / signoff / archive acce
That's how we are in one of our datacenters.
_
Dave Jousma
Assistant Vice President, Mainframe Engineering
david.jou...@53.com
1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H
p 616.653.8429
f 616.653.2717
-Original Message---
We're moving from a three CEC configuration, with all STP rolls,
Primary/Backup/Arbiter defined, to a singe CEC that's defined as the
Primary, with no backup or arbiter defined to the STP network. I'm not
seeing any additional risks, since we're already running in "all our
eggs in one basket mo
All of the recent COBOLs starting I think with COBOL for OS/390 have had an
entry point of IGYCRCTL.
IKFCBL00 is the entry point for VS COBOL I, often called CB1. The IBM program
number is 5740-CB1. It is a pre-LE product.
Compilers between CB1 and OS/390 *might* have also used IKFCBL00. If som
Correct. That's a very old COBOL compiler. Today's compiler is IGYCRCTL.
On Tue, Jan 19, 2016 at 12:58 PM, Ron Thomas wrote:
> I looked at the endevor processor group setting and it is showing the
> program that is used is PGM=IKFCBL00. is this won't work ? Thanks!
>
> --
I looked at the endevor processor group setting and it is showing the program
that is used is PGM=IKFCBL00. is this won't work ? Thanks!
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@li
The OP says "COBOL/DB2 program." I would wonder about DB2 support for the older
compilers.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Tuesday, January 19, 2016 10:00 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Let me also suggest you do not use the stand-alone external DB2 translator, but
use the SQL compiler option. Then any errors will be included in-line and it
will be easier to debug. Likewise the CICS compiler option vs the translator.
Also today, all the DB2 artifacts are GLOBAL such as the SQ
Interesting.It worked fine for me...
Regards,
Greg Shirey
Ben E. Keith Company
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Robert AH Prins
Sent: Monday, January 18, 2016 11:58 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: A u
It has been so long since I had a VS COBOL Manual, I did not recognize it.
So it seems what everyone is saying is
Fix would be to use a more current compiler.
Lizette
-Original Message-
>From: Pinnacle
>Sent: Jan 19, 2016 10:55 AM
>To: IBM-MAIN@LISTSERV.UA.EDU
>Subject: Re: Compile er
On 1/19/2016 10:23 AM, Ron Thomas wrote:
Hello
We are trying to compile a very old cobol/db2 program and getting the below
error . Could someone let me know how to get this fixed ?
00210 77 SQL-TEMP PIC X(128).
00211 77 DSN-TEMP PIC S9(9) COMP-4.
00212
On 19 Jan 2016 07:23:57 -0800, in bit.listserv.ibm-main Ron Thomas
wrote:
As others have pointed out the IKF messages are from an OS/VS compiler
(or another compiler set to the OS/VS mode). This compiler does not
recognize hexadecimal values. I'm surprised it isn't complaining
about the COMP-4 u
The first of two parts,
http://www.ibmsystemsmag.com/mainframe/administrator/workloadmanagement/DCOLLECT
-REXX/
outlined a basic understanding of the DCOLLECT record header and the various
methods to view individual DOCLLECT records. Part one examined the IBM IDCAMS
utilities and introduced a few
Quote vs. apost option?
Len Rugen
Metrics and Automation – umdoitmetr...@missouri.edu
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Lizette Koehler
Sent: Tuesday, January 19, 2016 9:32 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re:
What compiler are you using? The code looks OK for a _modern_ COBOL
compiler. I.e. for Enterprise COBOL (IGYCRCTL), but not for the older
IKJCBL00 compiler. The older compiler did not have hex literals. eg: X'00'
On Tue, Jan 19, 2016 at 9:24 AM, Ron Thomas wrote:
> Hello
>
> We are trying to com
What platform are you running this on? This does not appear to be COBOL
compiler on z/OS
An internet search on IKF1017I appears to be Hercules390 compiler? z/OS Cobol
is IGY typically.
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.
Hello
We are trying to compile a very old cobol/db2 program and getting the below
error . Could someone let me know how to get this fixed ?
00210 77 SQL-TEMP PIC X(128).
00211 77 DSN-TEMP PIC S9(9) COMP-4.
00212 77 DSN-TMP2 PIC S9(18) COMP-3.
00213
On Mon, 18 Jan 2016 18:32:28 -0500, John Eells wrote:
>the abilities to use SYMBOLICRELATE to point to a user catalog
>... were there
>from its inception many releases ago (well before z/OS V1.13).
Thanks, John. I never noticed the ability to use SYMBOLICRELATE
to point to a user catalog. I see
Hi James
You do not need to use /Service to perform mainmtenance.
You can mount your maintenance target HFS/ZFS files at ANY mountpoint, just so
long as your DDDEF PATH statements match.
You could even create mount points as /IPLVOL - same names as your IPL volume
VOLSER.
Hope that helps
Reg
In the past when we filed to dynamically add a SUBSYSTEM, I think we used a CBT
program to rename the bad SUBSYSTEM entry.
Then correct the reason it broke.
The ADD the subsystem again, no conflict as the subsystem entry had been
renamed.
Regards
Bruce
--
Morning,
If anyone feels they could vote on the RFE below it would be appreciated.
https://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=82636
It is a request to add the count of IXGCONN events to the SMF88 record
detailing system logger logstream activity.
regards
Steve
-
All couple data sets contain the sysplex name and can only be used in a sysplex
of that name, so they all have to be reformatted to define them with the new
name. In the IXCL1DSU JCL:
DEFINEDS SYSPLEX(newname)
Bill Neiman
Parallel Sysplex development
IBM
--
30 matches
Mail list logo
