Speaking as one who's been a systems programmer on multiple platforms,
installing via a package manager seems simpler than installing via, e.g., a
tarbal, zip filel. The only complexity that I see is installing an additional
package manager.
I use ArcaOS and openSUSE at home, and ANPM and Yast
I have just raised an RFE regarding support for better sharing of VSAM
system datasets (such as RACF, ICSF key stores and ZFS file systems) when
used in a sysplex with multiple master catalogs.
Please would you examine it and support of relevant for you.
Thanks
Lennie Dymoke-Bradshaw
https
I don’t disagree with using a package manager either. I embrace such in my
personal linux environments, where internet access is assumed. However, MF
space has been traditionally air-gapped so it just adds another layer of
complexity. Our installation happens to use Zscaler as our proxy pro
I have just raised an RFE regarding support for better sharing of VSAM
system datasets (such as RACF, ICSF key stores and ZFS file systems) when
used in a sysplex with multiple master catalogs.
Please would you examine it and support of relevant for you.
https://ibm-z-hardware-and-operating-sy
Lennie, I can appreciate your RFE, we used to maintain multiple mastercat’s in
our prod sysplex, but do not anymore.Mostly due to the extra efforts and
issues you note in your RFE. Our OMVS and CSF datasets are in usercats.We
do take catalog backups 4 times a day, and our master catalog
Classification: Confidential
In my experience, the 1st letter of the APAR name is a "version" designator.
e.g. JES2 has historically had many variants of a "single product".
So the APAR "documentation" designation would be OAx.
An actual "APAR FIX" (with test code) for the "1st version" would
On 11/5/2023 4:03 PM, Shaffer, Terri wrote:
So I am trying to apply maintenance and want to know the actual APAR to look up
to see if its open closed, or what?
Slide 72 in SHARE New Orleans Bit Bucket X'42' explains the APAR and
++APAR naming convention used most often with z/OS products and
Hello All,
I have been under the impression for decades that SYNAD exits are called in
24-bit mode.
Recently I have been having problems in one of my programs.
The problem goes as follows:
I am reading an input file that is defined as:
//INPUTDD *,SYMBOLS=JCLONLY
OUTPUT DATASET &OUTDSN *othe
Where did you specify your SYNAD exit? What was the AMODE when you issued the
GET or CHECK?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
From: IBM Mainframe Discussion List on behalf of
Charles Hardee
Sent: Monday
I’ve always gone to
https://www.ibm.com/support/pages/enhanced-holddata-zos and scrolled down
to “
*REPORT ERRSYSMODS APAR SYSMOD ID to RETAIN APAR Number mapping” to figure
out the mapping. *
On Mon, Nov 6, 2023 at 9:20 AM Ed Jaffe wrote:
> On 11/5/2023 4:03 PM, Shaffer, Terri wrote:
> > So
My notes from 2005 seem to imply that the SYNAD exit may be called in 31-bit
mode. I think it is called in the mode under which the GET or PUT was issued.
Charles
--
For IBM-MAIN subscribe / signoff / archive access instructions
To answer Seymour J. Metz's question first, it's specified in the DCB.
To answer Charles Mills' question, the module is defined as RMODE 24, AMODE
ANY, so the I/O was issued in 31-bit mode.
Which now rings a bell, I, too, vaguely remember that SYNAD is called in
the A-Mode of the code issuing th
> does this mean IBM has an issue in that they aren't clearing the flags
>from the DCB address when they load it for passing to the SYNAD exit, or is
>it my responsibility to clear the high byte
Not sure, but I can darn sure tell you what the fastest resolution would be!
Charles
On Mon, 6 Nov 2
Yep!
I've already done that, added an NILH to strip away the high byte, but it
does make for an interesting question.
On Mon, Nov 6, 2023 at 12:30 PM Charles Mills wrote:
> > does this mean IBM has an issue in that they aren't clearing the flags
> >from the DCB address when they load it for pa
On Sun, 5 Nov 2023 14:44:06 +0200, Binyamin Dissen
wrote:
>For example, it appears that ASSBRMA is pointing to the address space level
>blocks, but It isn't obvious to me what the block looks like.
Since no one has given you anything about RESMGR (and IPCS formatting), here's
my perspective fr
They can't strip the high bits without breaking the documented interface.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַי
From: IBM Mainframe Discussion List on behalf of
Charles Hardee
Sent: Monday, November 6, 2023 1:32
No; "Using Data Sets" documents the high bits of R0 and R1, so if you're
running AMODE=31 then it's your responsibility.
IMHO they'd have done better to have a SYNADX= parameter in the DCBE with a
fully 31-bit interface.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
עַם יִשְׂרָאֵל חַ
On Sun, 5 Nov 2023 00:20:52 +, Seymour J Metz wrote:
>IBM used to document how it assigned the prefix in sysmod ids, but its been
>decades since I've seen documentation that matched practice. What I've never
>seen violated is that the sysmod ids associated with an APAR all have the same
>nu
18 matches
Mail list logo
