The following is extracted (with apologies) from chapter 4 ETO Support V3R1
User's Guide for installing APPC/MVS components of this product:
//STEP1 EXEC PGM=ATBSDFMU
//SYSPRINT DD SYSOUT=*
//SYSSDLIB DD DISP=SHR,DSN=@@APPCTP
//SYSSDOUT DD SYSOUT=*
//SYSINDD DATA,DLM=’QT’
TPDELETE
Charles,
Before you get to far, unless things have changed, Metal C does not handle C++.
C only. I have not looked specifically at z/OS 1.13, but I do know that in
1.12
and earlier, C only.
Lloyd
- Original Message
From: Charles Mills charl...@mcn.org
To:
I did not find Kevin Kelley's post entirely persuasive. This
restriction long antedates 2 Kibyte pages, and the equation 8 x 4096 =
32768 is thus historically irrelevant.
Kevin was not trying to persuade. He was merely stating facts. The number
of pages is not the relevant part of the
In 51505550.8080...@dignus.com, on 03/25/2013
at 09:46 AM, Thomas David Rivers riv...@dignus.com said:
The DFSMS documentation states that using BLDL + FIND
(and using the ttr,C form for FIND) results in a performance
improvement... over simply pointing FIND at the DCB.
But - is that still
They ARE not.
Code has to be written to use PARMDD and will therefore not crash production
applications unexpectedly.
Modifications to current PARM could crash current code, running well for
decades based on ancient specs/assumptions.
Kees.
-Original Message-
From: IBM Mainframe
On Mar 29, 2013, at 07:46, Vernooij, CP - SPLXM wrote:
They ARE not.
The reference is elliptical.
Code has to be written to use PARMDD and will therefore not crash production
applications unexpectedly.
Only the JCL need change. If by code you mean load modules,
code needn't change.
On 3/29/2013 5:19 AM, Lloyd Fuller wrote:
... unless things have changed, Metal C does not handle C++.
C only. I have not looked specifically at z/OS 1.13, but I do know that in 1.12
and earlier, C only.
True in z/OS 1.13 as well.
--
Edward E Jaffe
Phoenix Software International, Inc
831
This thread has exhausted itself. We are rehashing trivia. I do not
need to be reminded of the capacity of a halfword, signed or unsigned;
and Kevin can defend his views himself if he wants to bother to do so.
For what it may be worth, I judge that the new facility is a happy
compromise of very
On 3/29/2013 6:46 AM, Vernooij, CP - SPLXM wrote:
Code has to be written to use PARMDD and will therefore not crash production
applications unexpectedly.
When I worked for a large bank, none of our production batch
applications were APF authorized. However, changes to production JCL
went
On Tue, 26 Mar 2013 23:09:16 -0500, Ed Gould wrote:
Paul:
I think you are reading too much into John's presentation.
After thinking about it I would guess that the exec statement and
parm will remain essentially the same and if you want to pass a
longer parm then you would code the exec
Test
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
resr
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
You failed that one.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Andy Robertson
Sent: Friday, March 29, 2013 9:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: test
resr
Uh oh, new GMail Reply format will irritate the bottom-posters -- now
it's non-trivial to not top-post. Let the flamewars resume.
On Fri, Mar 29, 2013 at 10:56 AM, zMan zedgarhoo...@gmail.com wrote:
And this is new how? :-)
On Fri, Mar 29, 2013 at 10:16 AM, John Gilmore jwgli...@gmail.com
Kenneth, lady and gentlemen,.
I do thankyou for your responses. There was much there that I have put to
use, SYSDSN, apostrophes, DELETE, use of EXECIO *, Got most of the coding
done, now to wait for mainframe access (hopefully IBM VIC), getting a good
lesson in 'proper'.REXX. Lizette, here in
15 matches
Mail list logo
