To help search engines: ABO = Automatic Binary Optimizer
>We haven't set off down the yellow-brick ABO road, so it's hard to gauge how
>much angst we'll actually have to overcome. I'm pretty sure it won't be
>trivial.
I haven't seen ABO in action yet. Is there a listing that relates the
> On Mar 26, 2017, at 11:27 AM, Bill Woodger wrote:
>
> Danger of this becoming another ABO thread in disguise :-)
>
> The question of the testing of ABO is not entirely cultural, or not
> necessarily so. Nor necessarily "compliance". There can be a technical basis
>
idfli...@gmail.com (scott Ford) writes:
> Bravo Phil and Tim from IBM. In my experience with NYC Stock Exchange
> and too many Brokerage houses to count, all of these installations had
> very tight internal/ external security. Including multiple firewalls
> to enter the MF domains. Once in the MF
Lizette
Thanks for your help with JES2 I got my SPOOL and CHKPNT data set off a
system pack and put them om work
Pack
thanks
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Lizette Koehler
Sent: Sunday, March 26, 2017 6:01 PM
To:
Thank you
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
Behalf Of Lizette Koehler
Sent: Sunday, March 26, 2017 6:01 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Help deleting file
Using 3.4 you can search the catalog (no volser) or volumes
Using 3.4 you can search the catalog (no volser) or volumes (complete or partial
volser)
If your dataset is cataloged but incorrectly
Go to TSO READY PROMPT
Delete 'dsn' NOSCRATCH NOPURGE <--- This uncatalogs the dataset
DELETE 'dsn' <--- this deletes the catalog entry
Then issue
I was able to uncatalog
But not catalog
Maybe the entry was just in the catalog and didn't
Exist
Subsqently I allocated it
Thank you very much
> On Mar 26, 2017, at 5:37 PM, Binyamin Dissen
> wrote:
>
> Uncatalog/recatalog
>
> On Sun, 26 Mar 2017 17:27:29
Uncatalog/recatalog
On Sun, 26 Mar 2017 17:27:29 -0400 Joseph Reichman
wrote:
:>Hi
:>
:>I'm getting a 213-04 abend on my ispf profile
:>Dataset
:>
:>It's seems to be a catch-22 where I can't delete
:>As the system cannot find it
:>
:>And I cannot allocate because the
Hi
I'm getting a 213-04 abend on my ispf profile
Dataset
It's seems to be a catch-22 where I can't delete
As the system cannot find it
And I cannot allocate because the system says it's a duplicate dataset
Doing a 3.4 I can see what pack it's on
Bravo Phil and Tim from IBM. In my experience with NYC Stock Exchange and
too many Brokerage houses to count, all of these installations had very
tight internal/ external security. Including multiple firewalls to enter
the MF domains. Once in the MF domain, the security subsystem was tightly
Danger of this becoming another ABO thread in disguise :-)
The question of the testing of ABO is not entirely cultural, or not necessarily
so. Nor necessarily "compliance". There can be a technical basis on which to
make decisions, which cultural and compliance issues may make moot. I'm keen to
The question of 'how much testing with ABO' is entirely cultural. No technical
expert can provide an answer satisfactory to all. At one end, you can argue for
minimal testing because application code has not changed, only the executables.
How many shops insist on extensive testing for updates
If you have very large programs and you want to optimise them to Level 1 or
Level 2, then Enterprise COBOL V6.1 is your best bet. The optimiszer was
re-written with 64-bit addressing and is now much more comfortable with large
programs (which may just fail to compile with V5.2).
V6.1 is now
I don't think you can order 5.2 any more. I recommend 6.1 especially if
you have large programs as the compiler is 64-bit and can compile much
larger programs.
Dan
On Sun, Mar 26, 2017 at 08:28 Charles Mills wrote:
> My *impression* is that many are skipping 5 and going
My *impression* is that many are skipping 5 and going straight to 6.1.
CharlesSent from a mobile; please excuse the brevity.
Original message From: James Wellingtin
Date: 3/26/17 7:46 AM (GMT-05:00) To:
IBM-MAIN@LISTSERV.UA.EDU Subject: Migrating
...contact me. We've done it a number if times.
Mitch
Mitch Mccluhan
mitc...@aol.com
On Sunday, March 26, 2017 James Wellingtin wrote:
Hey
I have posted this to the cicslist , and someone there asked me to post it
to this group as well for feedbackj
We are very
Hey
I have posted this to the cicslist , and someone there asked me to post it
to this group as well for feedbackj
We are very soon to migrate from COBOL ENT V4.2.0 to either Cobol 5.2. or
6.1
Do anybody have made any experience in doing that
Have you experienced any problem ?
Please describe
17 matches
Mail list logo