X" (from "Restructed EXtended
eXecutor.")
HTH
On 08/07/2022 03:12, Paul Gilmartin wrote:
> On Fri, 8 Jul 2022 02:38:38 +0100, CM Poncelet wrote:
>
>> Without meaning to bump into what might be off topic, SYSCALL is
>> actually a CLIST instruction - not a REXX on
Without meaning to bump into what might be off topic, SYSCALL is
actually a CLIST instruction - not a REXX one (unless it's a case of
"nous avons changé tout ça")
E.g.
HELP_SELECT: +
SELECT ()
WHEN (UP) DO
SET HPAN = - 1
*SYSCALL*
In the 1980's, IMS SYSMODs (CBIPO/CBPDO etc.) had to be accepted before
they could be applied. It might have had to do with the macros needing
to be accepted before the rest of it could be applied.
Not sure how it is done now. The last IMS *native SMP/E* CBIPO I did was
in 2000 - probably an
AFAIK An LMOD may have up to 64 aliases. How to alias it via a usermod,
I don't remember. I guess it could be done via an ALIAS linkage editor
control card (before the NAME card) and then figure out what the usermod
should be from there.
Anyway, I attach some assembler code (ALIASPDS.TXT) that
"every child has their " should be "every child has its
" - as "child" is animate but is also gender neuter
(regardless of political correctness and woke culture.)
On 09/06/2022 23:26, Bob Bridges wrote:
> That's mostly true. But that's the neuter gender, which in English we apply
> mostly to
OEM it. Rocket Software develops the OMEGAMON suite now.
>
> Matt Hogstrom
> m...@hogstrom.org
>
> “It may be cognitive, but, it ain’t intuitive."
> — Hogstrom
>
>> On Jun 4, 2022, at 9:07 PM, CM Poncelet
>> <03e99a92061c-dmarc-requ...@listserv.ua.edu&
FWIW I thought IBM had acquired BMC and its FileAid etc. But I seem to
be mistaken.
On the other hand, has or not IBM acquired Candle and its Omegamon? (I
worked with IBM and Candle in the early 90's.) TIA.
On 04/06/2022 03:14, Bill Johnson wrote:
> That’s exactly what I’m saying. Until
>From memory, the LEO (Lyons Electronic Office) computer of 1951/2 used
decimal (not octal or hexadecimal) digits. I cannot find a reference to
it, but this might help:
https://www.zdnet.com/article/inside-leo-the-first-business-computer/
https://en.wikipedia.org/wiki/LEO_(computer)
On
I cannot remember exactly where, probably in SYS1.PARMLIB(PROCnn), but
it shows the order in which PROCLIBs are searched by default for members
to be included during logons, STCs and job executions - with another
PARMLIB member showing which 'nn' PROC is currently active, or something
like that.
That's what I thought (VTOC and catalog updated) roughly. Thanks.
On 13/05/2022 05:33, Mike Schwab wrote:
> The VTOC and catalog is updated. SMS writes an EOF record on the
> first track, non-SMS gets the last contents.
>
> On Fri, May 13, 2022 at 3:52 AM CM Poncelet
> <
I could be wrong, but I had the vague impression that allocating
datasets via IEFBR14 did not *physically* allocate them on DASD - but
that they were physically allocated only when an 'OPEN for WRITE' was
issued against them. BTW I cannot check this, as I have no access to a
mainframe (8+ years.)
I cannot remember what the purpose was. I realise it is a bit odd to
have X2C(C2X(<...>)). Perhaps it was just to have the same X2C(<...>)
parms in the BITAND(): e.g. RB_TYPE_VAL =
C2X(BITAND(X2C(X_E0),X2C(RBSTAB1)))
On 20/04/2022 04:37, Tony Harminc wrote:
> On Tue, 19 Apr 20
FWIW No idea what "runarray" does, but attached is an example [in this
case for a CICS SVC dump] of some native IPCS REXX [as IPCSREXX.txt] -
which can then be modified to read/process any system dump.
BTW Was written to be executed from within IPCS - else add "ARG" and
"ADDRESS IPCS" etc.
+1
... and the GUIDE group then insisted that the new PL/I language should
also support COBOL's I/O processing as well as Fortran, at a 1962-64
conference (whenever it was.)
On 28/03/2022 10:43, Seymour J Metz wrote:
> I'm fully aware of the initial name; the fact remains that IBM and SHARE
> issue SVC 99 without calling assembly (the obvious choice in those days).
> PL/S would have done it more nicely, but PL/I had the facilities to make it
> happen.
>
> I often wonder why it wasn't more popular. C felt like a step backward.
>
> Roops
>
> On Fri., Mar.
hmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [03e99a92061c-dmarc-requ...@listserv.ua.edu]
> Sent: Wednesday, March 23, 2022 9:06 PM
&g
+1
It was initially called Fortran VI, because it was considered too
advanced to be called Fortran V (1962), then NPL (1964, but could not
because it was the acronym of the National Physical Laboratory [or
similar] in the UK,) and then PL/I - with the '/' from OS/360 and the
Roman 'I' to
schroe...@txfb-ins.com>
>
> 7420 Fish Pond Rd.
> Waco, TX 76710
>
> From: IBM Mainframe Discussion List On Behalf Of
> Ed Jaffe
> Sent: Thursday, March 17, 2022 9:16 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: SMF record - Looping and Memory shortage
>
&g
I can't remember the SMF record details, but the dispatch priority of
address spaces can be lowered 'on the fly' via SDSF (or CA's Sysview, if
memory serves) to swap them out and prevent them from grabbing storage
at the expense of what would now be higher priority ASIDs.
HTH.
On 17/03/2022
roadcast data set or in
> the receiver's user log
>
> SEND to console
> WTO; message retained in hardcopy log
>
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
> ________
> From: IBM Mainframe Disc
FWIW No idea whether this would help finding where TSOSEND data is
logged (try a GTF + parms, if 'critically important') - but I would
suspect that the data is stored in system genned temp datasets, possibly
in VIOs, and deleted after the data I/O sent-and-displayed on
terminal screens. Perhaps
Try something like this (syntax might need to be corrected):
//CHECKDEL EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
LISTCAT ENT(AA.AA),NAME
IF MAXCC NE 0 THEN DO
DELETE BB.BB NVSAM SCRATCH PURGE
DELETE CC.CC NVSAM SCRATCH PURGE
DELETE DD.DD NVSAM SCRATCH PURGE
SET
For what my memory is worth, I would suggest you begin by running a
'LISTVTOC' (using IEHLIST) and proceed from there. It *might* then allow
you to reset the VVDS and whatever else, provided you specify whatever
other parms for it (but probably not ones for IEHLIST.)
E.g.
Pictures (aka icons) are the preferred choice of those who cannot read.
On 22/12/2021 22:42, Tomasz Rola wrote:
> On Wed, Dec 22, 2021 at 08:04:01AM -0600, Dave Jones wrote:
>> "But I wonder, are we using all that computation effectively to
>> make as much difference as our forebears did
+1
On 22/12/2021 14:04, Dave Jones wrote:
> "But I wonder, are we using all that computation effectively to make as
> much difference as our forebears did after the leap from pencil and paper to
> the 7090?"
>
> IMHO, no.
> DJ
>
>
CTC's SPF/PC V4.0.7 could handle/edit/display/etc. hex data - but they
refuse to resurrect and republish their SPF/PC.
As for recovering from unwanted updates, try backing up your system
incrementally and before accepting any updates. I still use Norton's
Ghost V14 for that (i.e. for local
Yes indeed "PL/I is the only language you'll ever need" - other than
assembler and machine code.
It was initially called Fortran VI (1962), then NPL, then eventually
PL/I (with the "/" borrowed from OS/360 and the Roman "I" from Fortran
VI.)
It combined the numerical and formula processings
+1
BTW My TSO REXX began with IBM's MVS/XA in 1990 and not withMike
Cowlishaw's original 1984 REXX.
Rexx appeared, on TSO, somewhere in 1988/1989
On 19/12/2021 13:40, René Jansen wrote:
> My impression is that this sudden ‘article’ is linked to this ‘modernise the
> mainframe’ effort. It
Try this (attached): it worked OK in 1997.
Cheers, Chris Poncelet (retired sysprog)
On 14/12/2021 05:53, Weizman arbel wrote:
> hello ,
>
> i want to do this from batch.
>
> IEBPTPCH (PUNCH TYPORG=PO)
> add MEMBER NAME
> in front of each member
> and i want to prevent it.
>
> i did not
+1 ... and I worked for a couple of dozen banks and a dozen+ insurance
companies, and petrochemical and manufacturing industries, and
supermarkets and government agencies/departments, and for IBM and Candle
and the ESA and whatever other else - except for the kitchen sink.
On 12/12/2021 00:33,
Try coding "L R2,=V(TSAUXWRK)"
On 17/11/2021 22:50, David Spiegel wrote:
> Hi,
> I have been given a Load Module and source code.
> The Source Code, however, does not 100% match the Disassembled Load
> Module.
> This module has been running in production since 1994.
>
> With that preface
AFAIK The time of the Earth's rotation is not a constant, but is subject
to the variable position of its inner iron-core relative to the Earth's
geometric center. The closer this inner iron-core is to the Earth's
center, the faster too is the Earth's rotation - else, the further it is
from the
Hi Radoslaw,
If it helps, here is a link to the Washington Accord & its signatories.
You might want to follow up from there.
https://www.ieagreements.org/accords/washington/
Cheers, Chris
On 16/10/2021 12:28, Radoslaw Skorupka wrote:
> Definitely. When I see soldering, screws, etc. I
gt; On Thu, 14 Oct 2021 21:25:10 +0100, CM Poncelet wrote:
>
>> Anyone can call himself an engineer (e.g. a motor mechanic etc.) It is
>> illegal for anyone to call himself a *Chartered Engineer* (CEng) without
>> being qualified and registered as such with an accredited Enginee
Anyone can call himself an engineer (e.g. a motor mechanic etc.) It is
illegal for anyone to call himself a *Chartered Engineer* (CEng) without
being qualified and registered as such with an accredited Engineering
institution. HTH.
Chris Poncelet CEng MBCS CITP
On 14/10/2021 17:59, Radoslaw
Systems Programming Consultant or Technical Consultant (now retired)
On 11/10/2021 21:28, Herring, Bobby wrote:
> I asked this question back in 2004. My boss wants to know if there are any
> new titles to add to the list below.
>
> Mainframe Engineer
> Operating Systems Architect
> Software
This reminds me of someone at a Company I worked for, can't remember
which, where some programmer had displayed a prompt for whatever to
which an end-user replied "f*@k" - upon which the program then replied,
"Your place or mine?" Needless to say, management was not amused by this
and the
alpha bravo charlie delta echo fox-trot golf hotel india juliet kilo
lima mike november oscar papa quebec romeo sierra tango uniform victor
whisky x-ray yankee zulu
able baker charlie dog easy fox - were AFAIK part of the phonetic
alphabet used for the Allied invasion of Normandy in Operation
able baker charlie dog easy fox
On 04/10/2021 15:10, Paul Gilmartin wrote:
> On Mon, 4 Oct 2021 09:35:39 -0400, Bob Bridges wrote:
>
>> Ok, I give up. I have favorite-newscaster stories, too, but I don't get
>> this one. What's an EFT cargo hatch? Is this so obvious a failure that
>> I'll be
An EX 'dsn(member)' would require no /* REXX */ card if 'dsn' is
allocated to DDNAME=SYSEXEC in the user's TSO logon PROC, but would
require it if is allocated to DDNAME=SYSPROC in ditto.
The OS first checks whether a SYSEXEC DD is coded and, if yes, whether
the '(member)' is in it - and, if
The "/* REXX */" part is required only if the REXX exec is to be run
from a PDS allocated to DDNAME=SYSPROC instead of to DDNAME=SYSEXEC.
SYSPROC is for CLISTs, SYSEXEC is for REXXs.
On 29/09/2021 02:07, Andrew Rowley wrote:
> On 29/09/2021 6:54 am, Bob Bridges wrote:
>> Purely by the way,
LINE "( AGO .C )"
ISREDIT LINE_BEFORE .ZCSR = +
DATALINE "(.T ANOP )"
ISREDIT FIND EXECBASR 10 NEXT
ENDO
On 23/09/2021 18:15, Paul Gilmartin wrote:
> On Thu, 23 Sep 2021 16:33:34 +0100, CM Poncelet wrote:
>
>> To p
To prevent the command processor from substituting whatever looks like a
variable, code SYSSCAN={0||1|2|3}, then issue the (), then reset
to SYSSCAN=16 (default.) SYSSCAN=n means substitute up to n
SYSSCAN=0 means no & should be substituted.
To debug/trace, code CONTROL LIST SYMLIST CONLIST
In REXX, "ARG [template]" is just a short form of the instruction "PARSE
UPPER ARG [template]". Hence INTERPRET on passed ARG variables produces
uppercase results (unless PARSE ARG is coded instead of ARG).
There is no REXX equivalent to CLIST's "CONTROL CAPS ASIS".
CLIST:
A('SYS1.PARMLIB(IEAAPF00)') SHR KEEP".
BTW As I said, I have had no access to a mainframe for 8+ years. But
feel free to verify my adhoc sample *CLIST* code if you have access to a
mainframe.
Cheers, over and out.
On 13/09/2021 22:34, Paul Gilmartin wrote:
> On Mon, 13 Sep 2021 21:4
FWIW I attach what happens with REXX's INTERPRET vs CLIST's &&... (but
from memory, as I've had no access to a mainframe for 8+ years)
AFAIK, REXX's INTERPRET can handle only up to 3 or 4 levels of nesting -
as in INTERPRET (INTERPRET (INTERPRET etc.)) or similar - whereas CLIST
can retrieve the
is frustrating, hence my
> strong language. I will try to watch that in any future posts.
>
> Mike
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of CM Poncelet
> Sent: Tuesday, September 7, 2021 12:
To paraphrase Juvenal, "sed quis custodit ipsos custodes?" ("but who
guards the guards themselves?")
On 06/09/2021 21:15, Mike Hochee wrote:
> Just a word of thanks to the IBM heavyweights (Jim, Peter, Sri, et. al.) to
> whom a debt of gratitude is owed for their deep-water expertise, patience,
Exactly.
On 05/09/2021 00:55, Andrew Rowley wrote:
> On 5/09/2021 7:51 am, CM Poncelet wrote:
>> AFAIK The difference between RENT and REFR is that REFR pages (or
>> frames) can be stolen without their having first to backed up - because
>> they can be REFReshed from
ing
> those attributes. Jim Mulder has been at IBM for 42 years, so 1985 ... yeah
> he would've been working on MVS then.
>
> Thanks.
>
> Joe
>
>
>
> On Fri, Sep 3, 2021 at 9:05 PM CM Poncelet wrote:
>
>> At the risk of inviting 'flak', I suspect that there is a mis
.
On 04/09/2021 09:34, Andrew Rowley wrote:
> On 4/09/2021 12:05 pm, CM Poncelet wrote:
>> By definition, RENT and REFR modules should never modify themselves
>> (excluding the peculiar case of a RENT module that ENQ's on part of its
>> code, modifies it, restores it to wh
At the risk of inviting 'flak', I suspect that there is a misconception
of what RENT and REFR modules actually are.
By definition, RENT and REFR modules should never modify themselves
(excluding the peculiar case of a RENT module that ENQ's on part of its
code, modifies it, restores it to what
It can also be passed as ISPEXEC VPUT (var) SHARED - then VGET.
On 02/09/2021 13:52, Carmen Vitullo wrote:
> I've used the GLOBAL command before
>
> GLOBAL var1 var2 var2
>
> but I've had more success storing the variable in my profile pool
>
> ISPEXEC VPUT (var) PROFILE
>
> then VGET
>
>
>
lson wrote:
> CM Poncelet wrote
>
> The LP (load point) addresses of LMODs always end with x'000' (i.e.
> page-aligned)
>
>
> wanna bet?
>
> If this is what you have seen in all the dumps you have looked at, then
> you need to look at more dumps.
>
&
a page containing more than on load module? It happens
> all the time. Not all modules have or need a 4 KiB alignment.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-
FWIW and FYI.
A 31-bit instrucion is a 4-byte fullword address, as e.g. say at virtual
(DAT) address x'71234568'.
The first 3 nybles (x'712') indicate the segment from which the LMOD's
storage/address has been allocated.
The next 2 nybles (x'34') are the offset to the page within the segment
The bottom line is that the integrity/security of a current OS cannot be
reduced to a lower integrity/security level by upgrading it to a new OS
- as e.g. upgrading OS/390 to z/OS could not result in z/OS then being
less secure than OS/390.
Hence the argument that the integrity/security provided
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Friday, August 27, 2021 6:46 AM
&g
omatically.
Cheers, Chris poncelet (retired etc.)
On 27/08/2021 01:29, Paul Gilmartin wrote:
> On Fri, 27 Aug 2021 01:05:18 +0100, CM Poncelet wrote:
>
>> According to my OS/390 Collection March 1999 Version 2 Release 7.0:
>>
>> RENT: MVS *protects your module's v
ssion List" wrote on
> 08/25/2021 09:10:04 PM:
>
>> From: "CM Poncelet"
>> To: IBM-MAIN@LISTSERV.UA.EDU
>> Date: 08/25/2021 11:21 PM
>> Subject: Re: RENT binder option
>> Sent by: "IBM Mainframe Discussion List"
>>
>> II
tively treating everything in
> those ranges as conceptually REFR for stealing purposes,
> regardless of the load module attributes.
>
> Jim Mulder z/OS Diagnosis, Design, Development, Test IBM Corp.
> Poughkeepsie NY
>
> "IBM Mainframe Discussion List" wrote on
>
IIRC The page(s) of an LMOD marked REFR can be stolen without having
first to back it up to cache, because it can be REFReshed from cache (or
DASD) and continue to execute as if its page(s) had not been stolen -
e.g. in the PLPA. If it modified itself, it would hit a S0C4-4. AFAIK A
gt; http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Tuesday, August 17, 2021 11:28 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subje
variables embedded within the program
>> module is just the beginning.
>>
>> The bottom line is that Program Fetch allows RENT modules to be shared,
>> REUS is just a weird ENQ trick, and otherwise you get multiple copies. I
>> really don'
> module is just the beginning.
>
> The bottom line is that Program Fetch allows RENT modules to be shared,
> REUS is just a weird ENQ trick, and otherwise you get multiple copies. I
> really don't know if REFR has any effect over RENT. Perhaps it's required
> for PLPA modules.
>
>
BTW (off topic) REFR, not RENT, if a module's storage may *never* be
modified in any way.
On 15/08/2021 21:49, Bernd Oppolzer wrote:
> Many thanks!
> Very helpful and clear
>
> Am 15.08.2021 um 19:25 schrieb Peter Relson:
>
>> The rules for DELETE have existed unchanged for over 40 years (maybe
it to, but
without verification.
(e) Yes, alias names can be any characters (except spaces) and do not
have to be printable characters - same as SVC LMOD names.
HTH. Cheers, Chris Poncelet (r)
On 01/07/2021 13:28, Paul Gilmartin wrote:
> On Thu, 1 Jul 2021 05:38:48 +0100, CM Poncelet wrote:
>
&
FWIW Try using this (attached) - HTH - Chris Poncelet (retired sysprog)
On 01/07/2021 03:05, Joe Monk wrote:
> Yep, my bad.
>
> Didnt see that he was trying with a load module, for which the
> linker/binder is required.
>
> Joe
>
> On Wed, Jun 30, 2021 at 8:35 PM David Spiegel
> wrote:
>
>>
y and mediocrity) mainframe programming and in particular
systems programming. I call it the 'Pinocchio effect', whereby mainframe
sysprogs are offered beer and cigars in exchange for agreeing to be
turned into donkeys.
HTH
Cheers, Chris Poncelet (retired sysprog)
On 21/05/2021 21:20,
.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Friday, May 21, 2021 11:30 PM
rom: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Friday, May 21, 2021 10:43 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS
> Technologies
>
>
stompack stop having SMP steps?
>
> Yes, COND is easy to understand; it's also unnatural.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
>
> From: IBM Mainframe Discussion List on behalf of
>
Autocoder, 1401 Autocoder, MODSAP. SAAL, COMPASS and the usual D, F, G,
> H and HLASM.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
>
> From: IBM Mainframe Discussion List on behalf of
> CM Po
should not be working with mainframes.
Chris Poncelet (r)
On 21/05/2021 23:02, Seymour J Metz wrote:
>> ESA's OCO?
> What's that in reference to?
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> ________
>
;,
> and see the light come on in their eyes.
>
> But then, if PCs would have stuck with DR-DOS the mainframe would still be a
> more major player in the SMB business arena.
>
> Rex
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
>
ng new tools that I can ignore when they don't suit the task at hand.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncele
"I fear the Greeks and when bearing gifts."
On 20/05/2021 04:34, Paul Gilmartin wrote:
> On Thu, 20 May 2021 02:50:02 +0100, CM Poncelet wrote:
>
>> Again and with all due respect, progress is made not by blunting the
>> tool but by sharpening the user.
>>
ne is’
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> CM Poncelet
> Sent: 20 May 2021 02:50
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: JCL COND vs IF/THEN - Best catch up resources for MVS / ZOS
> Technologies
>
> Again and with all
nt as an email
attachment and wasn't correctly decoded)."
HTH.
On 19/05/2021 02:11, Paul Gilmartin wrote:
> On Wed, 19 May 2021 01:19:01 +0100, CM Poncelet wrote:
>
>> With all due respect, anyone who has difficulty coding JCL COND=
>> statements should consider *not* worki
> JCL I never used COND= again. IF/THEN is much
> easier to use and to explain to new people.
> I have seen many people code COND statements
> incorrectly because they did not acually
> understand how they worked.
>
>
> -Original Message-
> From: IBM Mainframe D
With all due respect, anyone who has difficulty coding JCL COND=
statements should consider *not* working with IBM mainframe systems.
All boolean conditional execution steps can be handled using only COND=
statements. I submitted a paper on this & it was published in
"Computing" in 1989. I would
Oops, missed that bit. In SMP/E, the ALIAS name(s) [up to 16] would be
specified via a SYSLIN ALIAS card during the link-editing of the object
modules and coded before the NAME card. Hence, via JCLIN. An IEBCOPY
COPYMOD would then copy also the names of the ALIASes, IIRC.
On 10/05/2021 23:04, A T
1024-byte long member alias names in a *PDS*? Perhaps now, or in Unix,
but not in 1988's MVS/XA or even in z/OS (whatever it was in 2013),
AFAIK .
On 10/05/2021 23:53, Paul Gilmartin wrote:
> On Mon, 10 May 2021 23:32:50 +0100, CM Poncelet wrote:
>
>> I attach the source code for alia
I attach the source code for aliasing members of a PDS.
Essentially, it just sets a flag in the COFT field of the directory's
ALIAS member and STOWs it.
Cheers, Chris Poncelet (r)
On 10/05/2021 23:04, A T & T Management wrote:
> Yes it is done by a BLDL and STOW underneith. But how
You bet. I worked with IBM Hursley (where CICS is developed) in the late
80's and early 90's, and CICS was and always has been pronounced "Kicks"
here in the UK.
On 10/05/2021 16:10, Joel C. Ewing wrote:
> IBM classes in US in early 1980's seemed to consistently pronounce CICS
> as C-I-C-S
I thought anything less than 7nm between a chip's 'layers' would
experience quantum effects, with unpredictable results.
Is this new 2nm chip for an IBM quantum processor?
On 07/05/2021 15:45, Bill Johnson wrote:
> This is huge.
> IBM says it has made a significant breakthrough in computer
Lately (sort of). I suspect Poncelet posted an old chart; no citation.
>
> People don't talk about SAA much nowadays.
>
> What about not functions but keyword instructions? Such as
>
> ADDRESS ... WITH
>
> Is that ANSI? SAA?
>
>> ____
J Metz wrote:
> CMS has CHARIN, CHAROUT, CHARS, LINEIN, LINEOUT, LINES AND STREAM.
>
>
> --
> Shmuel (Seymour J.) Metz
> http://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on beha
x
Cheers.
On 28/04/2021 03:46, Paul Gilmartin wrote:
> On 2021-04-27, at 19:53:31, CM Poncelet wrote:
>> Shared variable pools - as in VPUT/VGET SHARED - are supported.
>>
>> CTC's SPF/PC REXX supports Mike Cowlishaw's definition, as in his "The
>> REXX Lan
Shared variable pools - as in VPUT/VGET SHARED - are supported.
CTC's SPF/PC REXX supports Mike Cowlishaw's definition, as in his "The
REXX Language".
Table 3. Comparison of Built-in Functions
Availability of Built-in Functions
Function SAA
mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Monday, April 19, 2021 11:41 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: Print a SYSMDUMP
>
>
FWIW
Pre-IPCS, there was a TSO batch program to format SYSMDUMPs. I can't
remember precisely, but perhaps it was called something like AMSPRDMP or
similar.
With IPCS, there are lots of pre-written IPCS REXX execs available
somewhere (if memory serves, they begin with BLS*) and they can be
Backup using PGM=ADRDSSU with JCL (something like, from memory):
//BKUPSMPE EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//OUTDD1 DD DSN=(+1),
// DISP=(NEW,CATLG,DELETE),
// UNIT=CART (or similar)
//FILTERDS DD *
INCLUDE( -
.** -
.** -
)
//*
//SYSIN
om: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Tuesday, February 9, 2021 12:22 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LINK vs LOAD/CALL
>
> https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.3.0/com.ibm.zos.v2r3.ieab100/reus.htm
BTW Your 'refreshable' ...
PTR DCA(0)
label L R15,PTR
LTR R15,R15
BNZ CALLIT
...... Code that always leaves the same value in R15
://mason.gmu.edu/~smetz3
>
>
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Sunday, February 7, 2021 5:50 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LINK vs LOAD/CALL
>
> Of cou
3
>
> ________
> From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> CM Poncelet [ponce...@bcs.org.uk]
> Sent: Friday, February 5, 2021 9:57 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: LINK vs LOAD/CALL
>
>
No. RENT implies REUS. Meanwhile RENT *may* be modified IFF an ENQ is
first issued on the code to be modified, provided that code is then
restored to what it was before it was ENQ'd and then DEQ'd. Only REFR
prohibits any code modification (because REFR means that an LMOD can be
swapped out and
ws 10 64-bit. But it still works.
>
> Lennie Dymoke-Bradshaw
> ‘Dance like no one is watching. Encrypt like everyone is.’
>
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> CM Poncelet
> Sent: 27 January 2021 00:28
> To: IBM-M
I still have and use the last version of SPF/PC (4.0.7) from CTC. It's a
DOS program with an
in-built DOS extender. CTC stopped supporting it in the 1990's.
On 26/01/2021 15:21, PINION, RICHARD W. wrote:
> Does anybody remember an ISPF product that ran under mainframe Linux from
> the early
1 - 100 of 360 matches
Mail list logo
