Short answer - YES.
FC 9975 is basically to reduce the 'height' for shipping/delivery purposes i.e
if there isn't enough height clearance for the doorway. If a system is ordered
with this feature, it just enlongates the install time. Nothing to stop 'you'
to remove and reinstall the top bit. Ju
>Those were added w/ COBOL 2002, not 2014. Don't give yourself too much cre=
>dit!
I noticed that too, and thought I had corrected my post, but I guess I failed!
Cheers,
TomR >> COBOL is the Language of the Future! <<
I always use a single shared GLOBAL zone and multiple targets. It's much
simpler to keep track of and the only problem I have ever run into is a site
the IBM ran an audit on and they wanted to know why they had 8 LPARs but 24
target|dlib zones. Apparently IBM doesn't do it that way. Aside fro
Long ago in a galaxy far away, there was a telephone company called Gong, Owned
by Andromeda Telepath and Teleport. When a customer called in with an outage,
they would go to the appropriate equipment, clean and reseat all of the
contacts, and then test. They would then report back to the custom
I used to imagine the poor mechanics listening skeptically to a young clueless
driver saying "I swear, mister, it was making this awful noise just a minute
ago...!" I wouldn't have believed her either. Then I started in end-user
support.
I have implicitly believed those stories ever since. I
Heck, I was a PL/1 bigot from the start. There are other languages I like, but
I remember PL/1 with a kind of rosy glow - possibly because I never use it any
more.
---
Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313
/* I think everyone who chooses to stay out of politics (which is your r
I see bookkeeping issue to ensure that you IPL each LPAR from the correct
volume and to ensure that you install serive in the correct zone, but what is
the synchronization issue with rotating among a set of TARGET/DLIB zones and
associated volumes? Oh, there is a detail that I left out; the HFS
Defining BPXROOT according to documentation allowed this PTF to go on clean.
Thanks for the help talking it through,
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Jousma, David
> Sent: Thursday, June 11, 2020 1:11 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re
I lost faith COBOL and finallly became a PL/1 biggot when I was told that
ALTER GOTO was introduced to help support structured programmng :-)
Rupert
On Thu, Jun 11, 2020, 01:07 Tom Ross wrote:
> >The addition of EXIT PARAGRAPH
> >and EXIT SECTION have eliminated most of the reasons for use of G
Hi,
A bit of a niche question maybe, but this list usually enjoys those!
I need to move my z114, and sadly I don't have the possibility of
inspecting it physically right now. I was wondering if anyone knows if it
is possible to reduce the height of the z114?
In the IMPP there is a FC 9975 which s
Whether or not your methodology involves copying libraries or zones, you have
to be careful of everything. Every strategy has risks that you need to address.
There is no need to re-receive anything. You should, however, frequently
receive the HOLDATA.
--
Shmuel (Seymour J.) Metz
http://mason.g
? GTF? Generalized Trace Facility?
Is there another GTF in z/OS?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listser
Compartmentalization. Presumably the DFSMSdfp people don't talk to the OMVS
people.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dma
There are several strategies. I'd advice you to use a symbol to select the
default DB2. The key, however, is that whatever approach you use you think
through and document all the issues.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM
Yes, I think that is your issue.
Check BPXPRM00 for the SUPERUSER keyword. That userid has to exist, and have
UID 0
//
/* */
/* SUPERUSER is a 1 to 8-char
[Default] On 10 Jun 2020 17:14:25 -0700, in bit.listserv.ibm-main
tmr...@stlvm20.vnet.ibm.com (Tom Ross) wrote:
>>The addition of EXIT PARAGRAPH
>>and EXIT SECTION have eliminated most of the reasons for use of GO TO
>>in COBOL. I would be interested in any corrections to my
>>understanding by th
-Original Message-
From: Barry Merrill
Sent: Thursday, June 11, 2020 10:02 AM
To: 'pr...@videotron.ca'
Subject: RE: SMF 71 long floating point fields
To SAS, they are straightforward RB8. fields with exponent and mantissa.
SMF71AFB=80737.714286 RBCHAR=4513B61B6DB6DB6D
SMF71AFB=80700.14
So this is for DB2 software. Distribution libraries are *.AD* Target libraries
are *.SD*. So I would create a second target zone a define datasets and DDDEFs
for say "*.target2.SD*" ?
--
For IBM-MAIN subscribe / signoff / archiv
On Thu, 11 Jun 2020 18:57:12 +, Gibney, Dave wrote:
>
>The BINDER error is:
>IEW2821W DF39 UID 0 NOT PROCESSED. UNIX SYSTEM SERVICES FUNCTION GETPWUID
>RETURNED REASON CODE 0B4F0800 AND RETURN CODE
> 00A3.
>Likely due to this in the BINDER control statements:
>SETOPT PARM(PATHMODE(
I think I have it. I had noticed this new Healthcheck with z/OS 2.3 and I
intended to address it shortly.
BPXH081I The following problem was found with the SUPERUSER parmlib
statement:
UserID is not defined to the security produ
I am leaning toward what David had suggested - only based on the binder message
IEW2821W UID userid NOT PROCESSED. UNIX SYSTEM SERVICES FUNCTION
GETPWUID RETURNED REASON CODE reason AND RETURN CODE rc
Explanation: The value specified for UID is not a TSO/E user name or z/OS
UNIX user ID kno
Depends on your definition. (Is a zombie dead or alive?) We've run Catalog
Solution since Rocket was just gleam in someone's eye. We techs would love to
convert to Catalog Recovery Plus. Rocket has offered incentives to covert. Our
management doesn't seem to give a sh*t. CS is still supported. R
Hate to admit it, but I have UID(0) on my id at this time. And, I do have READ
to BPX.SUPERUSER.
I don't see any ICH messages in the obvious places
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Jousma, David
> Sent: Thursday, June 11, 2020 12:10 PM
> To: IBM
Are you permitted to BPX.SUPERUSER? Looks like you may not be?
IEW2821W DF39 UID 0 NOT PROCESSED. UNIX SYSTEM SERVICES FUNCTION GETPWUID
RETURNED REASON CODE 0B4F0800 AND RETURN CODE
00A3.
I am seeing this in the CAUSER report for an APPLY CHECK:
CAUSER FMID MESSAGE ID PAGE ERROR DESCRIPTION AND POSSIBLE CAUSES
UJ01705 HOT77B0 GIM23911E 16 LINK-EDIT PROCESSING FAILED FOR MODULE
FSUMXTSM IN LMOD FSUMSTSM IN THE SFSUMLIB
LIBRARY.
This list doesn't do attachments.
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Bill Giannelli
> Sent: Thursday, June 11, 2020 11:36 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: SMPe Apply not working
>
> I attached the apply check and the nonapply list
>
really need to see more than just your apply control cards, and IIRC that
APPLY PTFS for a new FMIND ( function ) will not apply the FMID you need unless
you specify APPLY FORFMID.
show the entire apply smpprts and smpout
show the FMID received successfully also
Carmen Vitullo
-
Apparently that world is not this world.
From: IBM Mainframe Discussion List on behalf of
Seymour J Metz
Sent: Thursday, June 11, 2020 11:51 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: "Everyone wants to retire mainframes"
> DBD or PSB library.
In a kinder,
I attached the apply check and the nonapply list
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
APPLY PTFS
BYPASS(
HOLDSYSTEM(ACTION,AO,DB2BIND,DEP,DOC,IPL,MULTSYS))
GROUPEXTEND CHECK .
--
For IBM-MAIN subscribe / signoff / archive access
Wrong Global zone specified?
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Bill Giannelli
Sent: Thursday, June 11, 2020 12:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: SMPe Apply not working
[CAUTION: This Email is from outside the Organization. Unless you trust th
You still end up with a major syncing problem using either Shmuel's or my
previous suggestion.
I personally have 1 set of target zones and a "canned" job to build an new
sysres from scratch using the SMP/E targets as the source.
I am happy to share the JCL if you would like.
HTH,
-Origina
Not sure I remember the details. I worked with one ex-sysprog that cloned the
SMP/E target environment to the sysres for documentation purposes (1980's.)
ZoneCopy should do a lot of what you seem to be looking for.
I (personally do not think that is the way to go. My suggestion is
One global zone
On Thu, 11 Jun 2020 17:47:46 +, Seymour J Metz wrote:
>I call that the "GTF effect"; the problem never manifests when I have
>diagnostic measures in place to capture failure data.
>
GTF? Generalized Trace Facility?
A colleague once used the term "Heisenberg effect" for a performance
monito
Those are not the messages I would like to see
1) Provide the APPLY Statement in full.
2) Provide all messages from the APPLY Function from SMOUT DD statement
This will help us see what the issues might be.
Sometimes when you do an APPLY it is for the incorrect FMID or the wrong SREL.
We woul
Nope!
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Seymour J Metz
Sent: Thursday, June 11, 2020 10:04 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Messages & Codes (was Re: "Everyone wants to retire mainframes")
[CAUTION: This Email is from outside the Organizatio
On Thu, 11 Jun 2020 11:40:47 -0500, Bill Giannelli wrote:
>So I've been reviewing the options you all have so kindly shares zonecopy,
>zonemerge, zoneexportand it seems obvious you need to be careful of the
>DDDEFs and renaming of datasets. If not careful you can really screw up and
>overla
Ditto, I'd like to also see what was actually received, this is a new product
IIRC, so did the FMID actually get received+PTF's ?
show what actually got received would also help
Carmen Vitullo
- Original Message -
From: "Dave Gibney"
To: IBM-MAIN@LISTSERV.UA.EDU
Sent: Thursday, J
The telephone folks used to close tickets with CWT -- "cleared while testing."
In other words, they could not reproduce.
Another support favorite:
Customer: You've got to help us. It's happening all the time. It's really
killing us. We're dead in the water without a fix.
Tech: Add a SYSUDUMP DD
If you stay current on HOLDDATA, which you should, then conditions will have
changed between the two sequences. You are not actually recreating your tested
maintenance environment into your production.
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Bill Gianne
And the output from smpout and smprpt
> -Original Message-
> From: IBM Mainframe Discussion List On
> Behalf Of Binyamin Dissen
> Sent: Thursday, June 11, 2020 10:57 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: SMPe Apply not working
>
> Show the APPLY statement.
>
> On Thu, 11 Jun
Show the APPLY statement.
On Thu, 11 Jun 2020 12:27:00 -0500 Bill Giannelli
wrote:
:>GIM59603IENQ WAS SUCCESSFUL FOR SHARED USE OF OEMPP.DB2.V12R02M0.SMPPTS1
FOR
:>GIM59603IENQ WAS SUCCESSFUL FOR SHARED USE OF OEMPP.DB2.V12R02M0.SMPPTS2
FOR
:>GIM24801S ** NO SYSMODS SATISFIED THE OPERA
There's another factor in the Betamax vs. VHS struggle. I went into a
department store to buy my first camcorder in the early 80s. I chose a Beta
model. The sales guy said, "Most folks these days are buying VHS. You can only
exchange tapes with the same technology. Pick out a VHS model. Take it
> DBD or PSB library.
In a kinder, more gentle world, the message would tell you which.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Frank Swarbrick [frank.swarbr..
I call that the "GTF effect"; the problem never manifests when I have
diagnostic measures in place to capture failure data.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf
Maybe the Zone is set to an incorrect Zone. (i.e SET BDY(TZONE).)
On 2020-06-11 13:17, Bill Giannelli wrote:
I ran a GIMSUP download, unpack, receive which ran clean. I see the received ptfs in a
LIST NOAPPLY. But when I run theAPPLY I get "NO SYSMODS SATISFIED THE OPERANDS
SPECIFIED ON THE AP
At least in that case you can hopefully reproduce the error :)
It's the one-time lost error messages that as a support person, you
sometimes have to say, "Oh well"
My favorite is when someone is repeatedly getting an error, but when
they call me over and without doing anything differently, the
Those were added w/ COBOL 2002, not 2014. Don't give yourself too much credit!
🙂
From: IBM Mainframe Discussion List on behalf of Tom
Ross
Sent: Wednesday, June 10, 2020 6:07 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Goto Statements AND COBOL OPTIMIZATION
GIM59603IENQ WAS SUCCESSFUL FOR SHARED USE OF OEMPP.DB2.V12R02M0.SMPPTS1 FOR
GIM59603IENQ WAS SUCCESSFUL FOR SHARED USE OF OEMPP.DB2.V12R02M0.SMPPTS2 FOR
GIM24801S ** NO SYSMODS SATISFIED THE OPERANDS SPECIFIED ON THE APPLY COMMAND.
GIM59606IDEQ WAS SUCCESSFUL FOR EXCLUSIVE USE OF OEM
Show us the output. Possible there are some control cards that are needed or
the PTFs do not match the SREL or FIMDs in your global zone.
But the GIM Messages would be very helpful to see
Lizette
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Bill Giannelli
Sent
I ran a GIMSUP download, unpack, receive which ran clean. I see the received
ptfs in a LIST NOAPPLY. But when I run theAPPLY I get "NO SYSMODS SATISFIED THE
OPERANDS SPECIFIED ON THE APPLY".
What could I be doing wrong?
thanks
Bill
My other favorite. We had someone call about an installation problem. The
solution was rather involved so our support tech said "it is covered in detail
in the Installation Manual" whereupon the customer guy said "oh, I don't have
the manuals. Bob has the manuals. He's in charge of documentation
Here are all of the possibly relevant parts from the JESMSGLG for a similar
occurrence that I just caused.
+*DFS0929I BLDL FAILED FOR MEMBER --ABCDEFG
IEA995I SYMPTOM DUMP OUTPUT 830
USER COMPLETION CODE=0929
TIME=10.52.44 SEQ=18497 CPU= ASID=0038
PSW AT TIME OF ERROR 078D1000 9012
What does the first byte look like, typically? I'm guessing 4X hex.
Cheers, Martin
Martin Packer
zChampion, Systems Investigator & Performance Troubleshooter, IBM
+44-7802-245-584
email: martin_pac...@uk.ibm.com
Twitter / Facebook IDs: MartinPacker
Blog: https://mainframeperformancetopics.co
My favorite is a marketing guy I was supporting. He called for my help with
some problem that had occurred - I don't remember what exactly, probably with a
DYL-280II program that he'd written with my help - and, as always, I asked him
what the error message had said. "Oh, it said some damn thi
So I've been reviewing the options you all have so kindly shares zonecopy,
zonemerge, zoneexportand it seems obvious you need to be careful of the
DDDEFs and renaming of datasets. If not careful you can really screw up and
overlay one environment.
While simplistic and perhaps slightly more w
I prefer to have a rotating list of TARGET/DLIB pairs, with symbols keyed to
the IPL volser. When I want to promote a configuration from, e.g., TEST to QA,
I just IPL.
Note that whatever methodology you you, there will be some bookkeeping
associated with it, and cutting corners can be fatal.
I do a similar process. One global zone for a z/os ver.rel, a "maintenance
zone", and then a target zone that matches every active SYSRES in my
environment. One DLIB zone.Maintenance is only actively applied to the
maintenance zone, and when ready to promote that level into use, I have a s
I would go for a shared GLOBAL and 3 TARGET/DLIB pairs. I would use REPORT
SYSMOD to help keep them in synch. Of course, often there are installation
standards in place as to maintenance methodology, and you can't change things
without getting the appropriate approval.
--
Shmuel (Seymour J.) M
I've done something similar but with one global zone and 2 target zones, one
for the current maint and one for the next maint - one DLIB zone, so one
global, one receive, apply to tzone1 migrate, then receive more maint, accept,
then apply to tzone2, something like that.
if you want a totally s
Well, in the TSO environment there's a service to build messages from
templates, plugging in variables. ISPF has similar services.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on
SMP/e ZONECOPY, UCLIN (to fix the DDDEFs), DFSMSDss to COPY and RENAME
the Datasets
On 2020-06-11 11:38, Bill Giannelli wrote:
I want to setup separate SMPe environments, say 3 for different maintenance levels. One matching production
then 2 others for maintenance levels "coming next". My ques
I want to setup separate SMPe environments, say 3 for different maintenance
levels. One matching production then 2 others for maintenance levels "coming
next". My question is, when I what to update my PROD environment with one of
the other maintenance levels, do I need to go thru receive, apply,
That's cool, the is/are and pluralization. I never bothered -- I have always
gone with (s) as in "You have %d dog(s)"
Yes, I really upped my error message game when I went from assembler to C++.
Yes, you can do anything in assembler, but unless you have or devote time to
developing macros such
Any message whose action is given as "contact your systems programmer" is just
as bad. Has IBM finally gotten rid of all of those?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on
When IBM started using pictures instead of text in their assembly instructions,
I coinded the phrase "International icons: unintelligible in any language." The
concept, of course, applies to software, not just to printed product assembly
instruction, and indisputably not just IBM.
BTW, would it
You have to understand national politics: "we won't buy this product; the
error messages are in English" [not French, Japanese, etc.]
Even though you are of course right, "diskette in drive" is more
understandable to the average French speaker than !! Sys01475
Charles
-Original Message-
On Thu, 11 Jun 2020 16:42:02 +0800, Timothy Sipples wrote:
>This pair of error messages was a design mistake:
>
>OS/2 !! Sys01475
>OS/2 !! Sys02027
>
>That's a case of national language considerations run amok. ...
>
>A diskette's boot sector doesn't have much room, ...
>:-)
Please don't try to j
This pair of error messages was a design mistake:
OS/2 !! Sys01475
OS/2 !! Sys02027
That's a case of national language considerations run amok. That was the
only pair of messages you saw on your screen when you formatted a diskette
with OS/2, left the diskette in the primary drive, and rebooted
69 matches
Mail list logo
