All disks larger than model-9 until model-58 (the max before EAV) are just
model-9's, only with more space. Nobody/software should notice the difference.
Our Sysres's are model-30's for many years after being expanded dynamically
from model-27's since we needed some more room.
Kees.
>
I have a question on PC instruction for which I have been looking for an answer
for quite sometime now. According to "Priciples of operations" manual,
execution of an SVC instruction causes a new PSW to be loaded from x'1C0' (SVC
FLIH), and program interruption causes a new PSW loaded from
AFAIK, SMS manages that DS1LSTAR is enforced when reading a dataset. That is
the difference between datasets on SMS managed and non-managed volumes. That is
also why an empty SMS managed dataset can occupy zero tracks.
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List
Hi All,
While applying RSU on zOS 2.2 I received
GIM23901E ** LINK-EDIT PROCESSING FOR SYSMOD UA80355 FAILED FOR MODULE
GFSAAOBT IN LMOD GFSAMAIN IN THE NFSLIBE LIBRARY. THE RETURN CODE (8)
EXCEEDED THE ALLOWABLE VALUE DATE 19.420 - TIME 11:52:10 -
SEQUENCE NUMBER 29
I am trying to
Thanks for your response. Yes I agree that PC doesn't involve any interruption.
"Principles of operations" manual clearly explains the PC translation process
but I wanted to know "Who" will perform this translation process? For example
we have "Dynamic Address translation" facility to transform
The difference is that is resolved by CAS, which is not yet initialized
at that moment. Until then, ** does the built-in substitution.
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Barbara Nitz
> Sent: 28 August,
A PC instruction is just an Instruction, not an Interrupt, so there is no
Interrupt handler involved and no new PSW loaded.
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of SUBSCRIBE IBM-MAIN Anonymous
> Sent: 28 August,
Well .
Actually most of a new PSW is loaded. The instruction address, AMODE and PSW
key may be changed.
The POPs describing the PC instruction goes into excruciating details on how
it works.
On Wed, 28 Aug 2019 07:03:38 + "Vernooij, Kees (ITOP NM) - KLM"
wrote:
:>A PC instruction
Thanks Barbara. Makes sense.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE | MD RSCB2H | Grand Rapids, MI
49546
616.653.8429 | fax:
I sit corrected. Thanks for teaching me something today.
Sent from ProtonMail, Swiss-based encrypted email.
GPG Public Key -
https://api.protonmail.ch/pks/lookup?op=get=markjac...@protonmail.com
‐‐‐ Original Message ‐‐‐
On Wednesday, August 28, 2019 2:15 AM, Vernooij, Kees (ITOP NM) -
On Wed, 28 Aug 2019 02:35:47 -0500 SUBSCRIBE IBM-MAIN Anonymous
wrote:
:>Thanks for your response. Yes I agree that PC doesn't involve any
interruption. "Principles of operations" manual clearly explains the PC
translation process but I wanted to know "Who" will perform this translation
This seems to be a lot of work to recover a very small amount of data.
There are so few options in the SADMP program, that it would probably be faster
to code it up from scratch.
Check the fine manuals for details on the macro coding.
HTH,
-Original Message-
From: IBM Mainframe
Volume and volume ** are equivalent. HLQ is a whole
different matter.
i.e.
DEF NVSAM(NAME(datasetname) DEVT(3390) VOL())
and
DEF NVSAM(NAME(datasetname) DEVT(3390) VOL(**))
Should resolve identically.
The "advantage of is that it is easily extensible to ,...
HTH,
Kirk Wolf wrote:
> Unfortunately, bash is pretty complicated software, and updating it to do
> this is not at all easy because of the difference in semantics between
> fork()/exec() and spawn().
Amen, brethren! :-)
Interestingly, it looks like there is exactly ONE call to fork() in the bash
Go find the output of the linkedit at sequence number 29. You will find the
actual error there.
_
Dave Jousma
AVP | Manager, Systems Engineering
Fifth Third Bank | 1830 East Paris Ave, SE |
I am beginning on an unsupported migration from MQ 7.0.1 to 9.1. Has anyone
done this before and have evidence that it does/does not work? Or am I looking
at recreating a whole new queue manager for V9.1? I would gladly jump
7.0.1->8->9.1 but it looks like 9.1 is the only version
I have never has a problem using anywhere ** could have been used.
Actually, the resolution of occurs very early in the IPL, long before
CAS is initialized.
HTH,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Vernooij, Kees (ITOP NM) - KLM
Sent: Wednesday,
On 2019-08-28 7:37 PM, Jerry Callen wrote:
Kirk Wolf wrote:
Unfortunately, bash is pretty complicated software, and updating it to do
this is not at all easy because of the difference in semantics between
fork()/exec() and spawn().
Amen, brethren! :-)
Interestingly, it looks like there is
Charles,
Exactly, what is being done under the covers, i.e; microcode etc ..
Scott
On Wed, Aug 28, 2019 at 10:49 AM Tony Harminc wrote:
> On Wed, 28 Aug 2019 at 09:59, Charles Mills wrote:
>
> > In answer to your question, I guess the answer is no. There is a DAT
> "facility" (some of us
Could there be legal issues? Does the UNIX® certification process allow the
default shell to be anything but Bourne?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
David Crayford
Sent:
Hi Allan,
Try using to Catalog SYS1.PARMLIB on the SYSRES and let me know
if it works.
In z/OS 2.1 it didn't.
Regards,
David
On 2019-08-28 08:35, Allan Staller wrote:
> I have never has a problem using anywhere ** could have been used.
> Actually, the resolution of occurs very early in
On Wed, 28 Aug 2019 at 09:59, Charles Mills wrote:
> In answer to your question, I guess the answer is no. There is a DAT
> "facility" (some of us remember when there was a DAT box!) but no, there is
> no named "PC facility" any more than there is a "BAL facility." It's just
> part of the
Curses: I do feel constrained by the characteristics of an antique device. I
guess that one man's Mede is another man's Persian.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin
In zOS, is it possible to extract a private key, making it viewable by a human,
generated by the RACF RACDCERT GENCERT command?
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to
I haven't had SYS1.PARMLIB on the resvol for years. That is the purpose of
SYSn.IPLPARM
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
David Spiegel
Sent: Wednesday, August 28, 2019 8:54 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Clarification on DASD mod
I feel it’s important how to use the instruction and it’s pros and cons.
I am not sure how important speed of instructions or width , halfword or
full word are that pressing of an issue with today’s processors, but that’s
my opinion.
Scott
On Wed, Aug 28, 2019 at 11:18 AM scott Ford wrote:
>
I doubt that PC was ever intended as a replacement for, e.g., BASR. How does
its performance stack up against SVC?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Christopher Y. Blaicher
Yeah, but, you said: "... I have never has a problem using
anywhere ** could have been used. ..."
Had you (or anyone else) placed SYS1.PARMLIB on your SYSRES, your
statement would not be completely true (for e.g. SYS1.PARMLIB)
On 2019-08-28 09:56, Allan Staller wrote:
> I haven't had
The agenda for the next Hillgang meeting is available:
http://www.vm.ibm.com/events/hill0919.pdf
Neale
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message:
PC and BAKR, which is another stacking type instruction, are not cheap. You
can do a BASR and STORAGE OBTAIN, STORAGE RELEASE and BR in less time than a
BAKR. I do not know for sure, but I would guess that 99% of what PC, BAKR and
PR do is millicode, and they do a lot.
Chris Blaicher
A PC is just, as the name implies, a 'CALL' instruction. Think of it as an
advanced and somewhat different form of Branch and Link (BAL). A BAL sets the
new instruction address; a PC may set the address, the AMODE, even the address
space.
The stuff described in the PoOp happens, just like it
On Wed, 28 Aug 2019 12:43:12 +1000, Andrew Rowley wrote:
>
>> ... I'm astonished and dismayed to
>> think that fork() is realized (sometimes) by sending imaginary cards
>> through an imaginary card reader.
>...
>Unix is sending everything through an imaginary teletypewriter, is there
>a
PoOps describes the DAT facility, but it doesn't, and shouldn't, describe who
implements it. Like DAT, PC, PR et al are black boxes; you are supposed to
program to the architecture, not to the implementation on any specific model.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
Correct me if I am wrong. I don't pretend to be an expert on this subject.
I think of SVCs as hailing from the era of centralized monolithic operating
system construction. I would guess that IBM had an "SVC number committee"
and they sat down and said "SVC 1 shall do this; SVC 2 shall do that;
My understanding was you needed to be on v7.1 to migrate to a more recent
version. This chart seems to support that.
https://www.ibm.com/developerworks/community/blogs/aimsupport/resource/MQ_migration/WMQ_Migration.pdf?lang=en
Back when I supported MQ, I had to migrate from v7.0.1 to v7.1
Hi Joel,
Yes, by exporting it to a dataset, PKCS12DER or PKCS12B64.
Make sure you set a password when you export.
https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.icha400/le-export.htm
– Vignesh
Mainframe Infrastructure
-Original Message-
From: IBM Mainframe
On Wed, 28 Aug 2019 16:13:36 +, Seymour J Metz wrote:
>Could there be legal issues? Does the UNIX® certification process allow the
>default shell to be anything but Bourne?
>
POSIX requires in some cases that it not be Bourne. POSIX shell requires
tilde expansion, absent in Bourne shell.
Never measured SVC vs PC. While in some cases PC and SVC are similar, in many
ways PC is far superior to SVC. It can be local or globally defined and it can
be dynamically defined and removed. (OK, so can an SVC be added and deleted,
but I think PC's are easier).
Also, an SVC can't do space
PC has a larger address space, but IBM still has to reserve numbers for its own
use, and 3rd party vendors still must avoid collisions.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Charles
An SVC can schedule an SRB into another address space; that may be more
overhead, but it's still space switching. But, yes, there are far fewer use
cases for new VCs these days.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM
System symbols are defined IEASYMxx, which resides in (some) PARMLIB as
specified in LOADxx. I don't think you can resolve a system symbol whose
location is itself determined by IEASYSMxx until you have found and read that
SYM member.
My personal preference for a variety of reasons is to keep
As I said before, that is the reason for the existence of SYSn.IPLPARM. To
locate SYS1.PARMLIB when it is not on the sysres (among other things).
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of
Jesse 1 Robinson
Sent: Wednesday, August 28, 2019 11:54 AM
To:
One other advantage of PC over SVC, you can issue them in SRB mode. A very big
thing if you are running on zIIP processors.
Chris Blaicher
Technical Architect
Syncsort, Inc.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Seymour
Exporting the private key is only possible if the keys is NOT stored in the
PKDS. So the certificate would have been defined without using the PKDS, ICSF
and PCICC options in RACDCERT.
Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd
Web: www.rsmpartners.com
‘Dance like
Hello folks,
I have a question and precious little information.
We use CDC IIDR to support replicating VSAM file updates downstream from
our CIC applications.
We have a LOGSTREAM defined in the Coupling Facility of our SYSPLEX.
Apparently, there is a VSAM file that is defined behind the CF
I'm sure everyone is tired of this thread but I wanted to jump in here and say
that anyone -- including me -- who said "you should never get a private key
from the owners of some server you want to connect to" was potentially wrong.
Yes, yes, of course, sending out root CA or Intermediate
For "who will perform the translation process", it's not going to be clear.
First, rather than translation, the PC instruction builds the environment from
the token. ETDEF defines the PC environment but ETCRE or ETCON could easily
insert calls into the environment entry without us being
The PC instruction is a replacement for SVC. Both instructions exist solely
to run authorized programs in other address spaces. PC was designed to fix and
simplify many of those problems with SVC. Some of the important problems
addressed (not all):
1. 256 static defined SVC's replaced by
Hi David,
Thank you so much
I was able to track down via the sequence number and it turned out to be a
DDDEF missing.
I did receive another related message for RMF module but I feel it's a
packaging error and I would like to get an opinion on this
For example
UA91794
Message ID : GIM23901E
PC does not have a larger address space. It simply has the option to access
other address spaces.
Collisions for PC environments cannot occur because the PC instruction must use
the token returned when you created the environment. The problem is passing
this token to programs issuing the PC
Hi All
Cross posted
I am working on a CICS VR implementation. Below documents suggest that I
place CICS VR shipped module DWW1VS00 ahead of DFSMS related DWW1VS00 in
LPA order.
Will there be any impact to DFSMS if i place the CICS VR module ahead of
SYS1.SDWWDLPA ?
Please "contact your friendly IBM representative" if you want to
investigate whether it's possible to place a special order for some
intermediate MQ for z/OS release, such as 7.1, to facilitate your upgrade.
Planning information for migration from Version 7.0.1 to 7.1 is available
here for
The url
https://www.ibm.com/support/pages/pdse-member-pending-delete-processing-over
view indicates that when executing IEBPDSE with the
PARM='PERFORMPENDINGDELETE,NOANALYSIS'
Seems to imply that space will be released for deleted members. We do
routine maintenance on various Linklist datasets
>I have never has a problem using anywhere ** could have been used.
>Actually, the resolution of occurs very early in the IPL, long before
>CAS is initialized.
>
>The difference is that is resolved by CAS, which is not yet initialized
>at that moment. Until then, ** does the built-in
What if the res volume is spreaded on two volumes ? Can we still use
'**' ?
On Thu, 29 Aug, 2019, 9:17 AM Barbara Nitz, wrote:
> >I have never has a problem using anywhere ** could have been
> used.
> >Actually, the resolution of occurs very early in the IPL, long
> before CAS is
>What if the res volume is spreaded on two volumes ? Can we still use
>'**' ?
No, not according to how I read the book. Only the data sets on the volume that
you specify in the IPLPARM can use **. Any other volume containing non-VSAM
system data sets would be considered an *extension*
Hello,
Does anyone know the command to make a DASD VOLMUE online and available to
MVS w/o an IPL after the Attach command in Z/VM?
If I :
1- Att A1D MVS (I already created a muti path relationship via DSF)
2- ??? Which MVS command makes it available to use in MVS? ( I need
to
Hi Carlos,
V xxx,ONLINE
(where xxx is the Virtual Address of the ATTACHed DASD).
Regards,]
David
On 2019-08-28 21:23, CarlosM Martinez wrote:
> Hello,
>
> Does anyone know the command to make a DASD VOLMUE online and available to
> MVS w/o an IPL after the Attach command in Z/VM?
>
> If I :
>
>
Thanks everyone for all your inputs.
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
59 matches
Mail list logo
