And what does this have to do with the discussion of PTF level in SYSPRINT?
I believe this should have been Rexx substr not retiring string (sic)
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
On Behalf Of Paul Gilmartin
Sent: Thursday
The locution nul character, x'00' (SBCS) or x'' (DBCS) is
unobjectionable. It is in wide use. The C string of 'conceptually
unlimited' length is delimited by a null or a null character.
A null|nul string is one of length zero. To say more is to descend
into implementation detail, though
On Wed, 2 Apr 2014 11:45:36 -0400, Tony Harminc wrote:
On 2 April 2014 06:04, Sharuff Morsa3 wrote:
It is interesting to note that the IBM Installation manager is fast
catching up on installing...
http://www.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP102014
On 2014-04-03, at 10:46, John Walker wrote:
Is the null character termination of execio a new thing, or just something I
was not aware of before this? Unfortunately, with the new crowd of pc-minted
programmers taking over in the mainframe realm, we are likely to see more and
more datasets
I am out of the office until Tuesday - Dan Smith is in charge in my place.
Thanks,
Joey
2014 (#2014-62)
LISTSERV at the University of Georgia
ASSEMBLER-LIST Digest - 1 Apr 2014 to 2 Apr 2014
(#2014-62)
Table of contents:
PTF level in SYSPRINT
(6)
CPU Measurement Facility
Documentation (2)
Rexx substr not retiring
string
PTF level in
SYSPRINT
PTF level
Gil
If you (or anyone on the list) would like to see the PTF level in a GBLC
symbol, or indeed, any other useful piece of information in a system GBLC,
simply raise a requirement (go read
http://www.ibm.com/support/docview.wss?uid=swg21577670 on how to do raise
one).
And as Jonathan mentioned,
Ref: Your note of Tue, 1 Apr 2014 19:26:04 -0700
The HLASM product has always used a single chain of maintenance
rather than a tree, and provided the INFO option to list the
product changes. I don't know the specific reason that this
choice was made, over 20 years ago, but as HLASM uses common
Storm warning of pedantry to follow
Sharuf Morsa's characterization of system variable symbols (like
SYSDATC) as 'GBLC symbols' is not quite right.
They are not global character set symbols. They cannot be set by a
programmer at all; some have local and some have global scope; some
have
(overriding the personal Reply-to: -- others might value replies.)
On 2014-04-01, at 20:26, Jon Perryman wrote:
This means a PE'd PTF will hold up ASM maintenance until the fixing PTF
becomes available. It also means we can't install a PTF to fix a specific
error. Does the ASM group ship
On 2 April 2014 06:04, Sharuff Morsa3 sharuff_mo...@uk.ibm.com wrote:
It is interesting to note that the IBM Installation manager is fast
catching up on installing, tracking products and service levels - and is
being used by WAS on z - see:
I seemed to have botched SharufF Morsa's name, for which I apologize.
In mitigation I can only plead that two of my former students, one
Pakistani and one Persian/Bahktiari transliterate their names as
'Sharuf' with only one 'f' and that I had never before seen this
transliteration.
John
Ref: Your note of Mon, 31 Mar 2014 23:26:21 -0600
Paul Gilmartin paulgboul...@aim.com writes:
(Motivated by a thread in IBM-MAIN.)
I notice that the HLASM PTF level appears on the first page of
every SYSPRINT.
Does this imply that there is a unique CSECT updated by every PTF?
Module
On 2014-04-01, at 02:46, Jonathan Scott wrote:
Ref: Your note of Mon, 31 Mar 2014 23:26:21 -0600
Paul Gilmartin paulgboul...@aim.com writes:
(Motivated by a thread in IBM-MAIN.)
I notice that the HLASM PTF level appears on the first page of
every SYSPRINT.
Does this imply that there is
Ref: Your note of Tue, 1 Apr 2014 05:09:21 -0600
Paul Gilmartin paulgboul...@aim.com writes:
...
May I have your permission to quote you on IBM-MAIN?
I hope I wouldn't say anything on this list such that I would
have any problem with it being quoted elsewhere!
The fact that ASMA9Z and
This means a PE'd PTF will hold up ASM maintenance until the fixing PTF becomes
available. It also means we can't install a PTF to fix a specific error. Does
the ASM group ship APAR's to allow specific problems to be resolved without
applying all PTF's?
The C compiler list 4 PTF's as the
(Motivated by a thread in IBM-MAIN.)
I notice that the HLASM PTF level appears on the first page of
every SYSPRINT.
Does this imply that there is a unique CSECT updated by every PTF?
Implying that each PTF has its immediate predecessor as a PRErequisite?
Implying, in turn, that the graph of
17 matches
Mail list logo
