Final update:
Mike Rydberg was 100% correct - 'SL Prot' was set to, 'Y' and, as soon as
this was reset to, 'N' I had no problem at all creating an unlabelled tape.
I found copies of the 9840 Product Manual and User Reference Manual here ...
... or a very garbled version of the story that the original IEFBR14 didn't
clear R15 and so, 'completed' with a non-zero return-code ...
It's said that two APARs have been accepted against IEFBR14:
1) Non RC=0 problem
2) Not link-edited as reentrant so not available as candidate for LPA
Quite
Just a thought ... you're not trying to share DASD between the z/OS (MVS)
systems in a, 'risky' way, are you?
(Even more bizarre thought - you're not trying to share paging volumes
between your z/VM systems, are you? This would certainly provide many
opportunities for virtual machines to crash in
to achieve what you wish to do but ... in the
meantime ... yes, each PERFSVM requires a separate 191 (and 195) minidisk.
Regards
Jeff Gribbin
Thankyou Mike for that info ... I'll get the firmware levels checked out.
Update for any viewers / interested parties; this morning, for a short
while, the drive behaved itself and I was able to write to it using TAPE,
PIPE and MOVEFILE ... then it once again, 'just stopped working' ...
symptoms
Success (of a kind):
Rewind the tape
TAPE MODESET ( 3590C
TAPE WVOL1 volser
REW 181
TAPE FSF
Write whatever I like on the tape without problems
If I attempt to write anything other than the volume label (using TAPE
WVOL1) at the beginning of the tape then the write fails.
My tape operator has
-checked and is definitely set for write-permit.
I'm hoping that maybe somebody did discover a resolution but for whatever
reason it either didn't get posted or I've been looking in the wrong plac
e!
Thoughts, anybody?
TIA
Jeff Gribbin
Hmm - thanks for the hint ...
From OPERATOR ...
HCPERP584I TAPE 0500 AN OPERATION WAS TERMINATED BECAUSE A
HCPERP584I CAPABILITY CHECK OCCURRED
HCPERP6300I SENSE DATA FORMAT = 04 MSG CODE = 01
HCPERP6301I CHANNEL COMMAND WORD
Thanks for the thought but I don't think that's it - there really is just
one tape drive and it's in regular use from the z/OS LPARS.
I HAVE (just) successfully used TAPE WVOL1 volser to write a VOL1 label o
nto
a tape - this was part of a double-check that the tape WAS fully rewound
prior to
I'm thinking, 'AUTO_IPL parameter on FEATURES statement missing in SYSTEM
CONFIG on the 6.1 system'
IIRC, the system does not ship with AUTO_IPL enabled - you have to make that
change yourself.
Example (fragment) from a SYSTEM CONFIG near me ...
Clumsy phrasing on my part (slapped wrist accepted) ... should have said,
'No longer supports real 1403'.
Apologies for lack of precision.
received :-)
Regards
Jeff Gribbin
As usual, the solution is simple and (with hindsight) obvious ...
z/VM now only supports 3203 printers
Change directory to
SPOOL 000E 3203 A
and it all works just as one would expect.
Thanks to Tom Paul for his (off-list) discussion of the problem - he helped
me to, 'emiminate the impossible'
Dennis - I shall suggest that the requirement is therefore appropriately
qualified. I still wonder where DEFINE MDISK comes into the picture.
Just to round this off ...
Installation completed successfully, exactly as per the manual. I now have
a base-level system installed from an FTP server and upon which I shall soon
install an up-to-date RSU.
Note that 2nd-level userid used for installation is a Class G userid with no
privs - I
Hmm - In the words of Tom Wolfe, I'm either, 'Stretching the envelope' or
I've, 'Augured in' ...
For the first time, I'm attempting a z/VM 5.4 installation 2nd level from
an
FTP Server Directory (as opposed to straight off the DVD or via DDR).
Irrelevant but maybe of passing interest, the FTP
Hi Malcolm,
Did you see/do the top of page 70:
If installing from a:
...
FTP server directory, upload the contents of both the z/VM system
DVD and the RSU DVD to a new directory on the FTP server.
...
Upload the contents of each DVD to the directory. After the
I've dug around in the EXECs - two points come to light ...
I failed to invoke DVDPRIME with the, 'server' option ('DVDPRIME ( SERVER')
- therefore :DVDSOURCE in £PRIME£ £FILE£ was loaded with, 'DVD' rather than,
'SERVER' and consequently INSTDVD was not aware that it should skip the RSU
?)
Feel free to say, 'None of your business!' if you wish!
Regards
Jeff Gribbin
(I'm guessing he uses it to line the bottom of Chuckie's cage g)
... and good stuff too from Melinda Varian and others on the Distribution
Page ...
http://vm.marist.edu/~pipeline/
http://vm.marist.edu/~pipeline/#MWV
All I can say is: wow. You guys got REALLY lucky.
What's that old saying about, 'The harder I work the luckier I get'?
It looks to me as though IBM engineers really, 'lucky' equipment. g
Brilliant feedback - thanks - it's good to see that this has blossomed in
to
something that is at-least potentially useful to more folk than just myse
lf.
Just to update my personal progress, I've successfully built the second
stack and then, because I was able to now access the system through
forgive
Greetings,
I may be a, 'VM-Oldie' but I'm most certainly a, 'TCP/IP Newbie' and, tru
e
to form, I'm already wishing to push the envelope a little ...
I'm helping to maintain a not-very-busy z/VM system which is pretty-much
starting from scratch and currently has no asociated SLA's or the such to
:-)
(Exits I shall leave as an exercise for another day)
There's no doubt that, if you can afford it, it's a good idea to take
one of the commercial options.
Failing that, I'd strongly recommend having a look at the PIPELINE
stage called STARMON - it's very easy to set up a data-collector based
around STARMON.
(A search of the archives using the
Do you already have a z/VM system? If yes, you'll certainly have no
problem installing the new z/VM in a virtual machine using 3390-9
sized minidisks. Then, once installed, you can DDR the packs onto the
starting cylinders of, 'dedicated' volumes (or even better, complete
the configuration work
. I *know* he doesn't look like that anymore. He's
obviously a teacher of some sort, demonstrating important university
research techniques. And who's that in the background? Looks like
Stuart McRae.
-- R;
On Fri, Jan 21, 2011 at 10:55, Jeff Gribbin jeff.grib...@gmail.com wrote
... to http://web.me.com/melinda.varian/
Greetings,
I've been playing around in my sandpit again and could, once more, do wit
h
confirmation of what I appear to have learned ...
The objective of my playing around was to gain experience (2nd-level) in
using the (HMC) Integrated 3270 Console. All 2nd-level ...
Logon 2NDLEVEL userid
TERM
I've been hunting the doc's for more detail on how SIGNAL SHUTDOWN actual
ly
works - assuming that somewhere the process would be documented in terms
of
what the to-be-signalled guest has to do to establish the environment and
how CP actually transmits the signal to the said guest.
So far no
Thanks guys - never would have found that by myself. ZArchitecture POP is
n't
exactly explicit on the matter but from a reading of SHUTTRAP and a readi
ng
of POP I now see it to be a form of the Service Signal External Interrupt
.
Happily I don't need to code a handler solely from the information
Just a question of courosity, are you interested in a CMS application or are
you looking for something in a different OS, ie zLINUX or zVSE?
I'm currently writing a z/VM Overview course and - once again - the
truism that, 'the best way to learn a subject is to teach it' applies
... I've known
and hunt down
those routines for you then I'd be happy to do so - just contact me off-list
and I'll be on my way :-)
Regards
Jeff Gribbin
responses ranging from, Don't even THINK about it!
through, It's possible but only a masochist would do it and, It can be
done but there are restrictions up to, It's a breeze - just follow the
rules.)
In the hope that I'm not stirring up a hornet's-nest and with thanks in
anticipation.
Jeff Gribbin
Thankyou Alan - that succinctly lifts my understanding to the level
of, It's physically possible but really, really inadvisable because
... followed by exactly the concerns that I would have felt compelled
to raise here had the consensus been that it really was as easy as the
manual appears to
:-) ('nuff said)
I'm tempted to suggest that anyone who likes this strategy but didn't kno
w
about it should send in a Reader's Comment on, 'z/VM Installation and
Service' - but I don't want to swamp the Pubs Folk with a pile of individ
ual
comments, each of which they'd then have to answer, so
Hmm ... stranger things HAVE happened ...
:-)
Academic question that does not appear to be answered in Principles of
Operation - can anyone help?
Principles of Operation doesn't seem to mention how a program (operating
system), 'reads' the loadparm - and CP Commands and Utilities (IPL comman
d)
isn't very helpful either ...
snip
The load
Mike,
It falls into the category of, 'Just curious'. I suspect that along with you
and many (most?) others on this list I'm from a generation that's allergic
to, 'smoke and mirrors'. I'd always assumed that the answer was simple,
obvious and documented in Principles of Operation. I had occasion
It is obtained using a mechanism that is not published beyond its use in
Linux. The best you can do is RTFC, and it is not a trivial process.
Alan Altmark
Thankyou, Alan, for a definitive reply. What a strange thing to keep secret!
Regards
Jeff
Can anyone recall offhand when RSCS Version 2 (the first one to run under
GCS rather than standalone) first shipped?
I'd offer a free beer at SCIDS to the first person to respond with a
verifiable and correct answer, but I understand that such behaviour is
discouraged nowadays.
Again, TIA.
Earliest possible is 1985 and VM/SP Release 4 (first ship of GCS) but I h
ave
a nagging feeling that it shipped later and we started out on VM/SP Rel 4
with RSCS V1.
For once, Mother's History didn't give me the answer ...
Not really important - for my needs, 'A Long Time Ago' will do - it's
Tom,
SC24-6098 z/VM Group Control System.
Search for, 'Single User Group'. I've only skimmed it but it basically lo
oks
to me as if you just run RSCS in what would normally be the recovery
machine. Should simplify things a bit for those who only need GCS for RS
CS.
Hi Berry,
It would seem that we think along similar lines - I went to the Service
Guide and decided that SYSTEM NETID would be a replacement-maintained par
t -
but SES didn't seem very impressed when I followed the, 'replacement'
process in, 'Procedures for Local Service and Modifications' in
If one was looking for the, 'official', 'approved' technique for changing
(say) SYSTEM CONFIG (or some other file on MAINT CF1) or even SYSTEM NETI
D
S2, where would one look?
Please note, I'm not asking for suggestions on safe ways to do this - I c
an
generate no end of those for myself (as my
Map the disks as provided by IBM - in previous releases the last cylinder
has deliberately been left unallocated - this allows you to create
(nearly) full-pack minidisks at cylinder 1 of a real volume (through to
the end of the volume) and then restore the whole of the, starter onto
those
Only half!?! grin
There's a risk / benefit tradeoff here; but it's quite possible to have
SPOOL minidisks at second level with the same virtual VOLSERs as the real
SPOOL volumes so that the, look and feel of the updated system is akin to
the production system. It's not how I would have done it but it's perfectly
Franz Josef,
If you move your production SPOOL to dedicated volumes, along with your
WARMSTART / CHECKPOINT areas then, unless the format of the SPOOL control
blocks changes (a rare occurrence and one which is always flagged in the
documentation when it happens) you shouldn't need to restore the
No-such-thing-as-bad-publiciy-dep't ...
Well, my brother's been enjoying a mini-boom of interest in his books ever
since the photo of, Get a Grip on Physics (in the back of Tiger's car) was
published on (among others) the WSJ website. grin
Cheers
Jeff
to get at any bits
that need fixing.
Bon Chance!
Jeff Gribbin
Mike (Walter),
I suspect that you're quite correct, the, MOVINGON reference is perhaps
now dated - or at least inappropriate for use by retirees. I won't
apologise for using it (not that anyone would expect me to) because I'm
far too much of a sentimentalist to not allow the chance for a
Friends,
At the end of this week, my time with EDS will be up. I expect to be
moving into some state of partial-retirement and, as-yet, it is unclear
whether or not, IBMVM will form a part of my professional future.
(Indeed, it's unclear exactly what kind of, professional future, if any
,
I
... and, to be fair to IBM, this behaviour, and how one should respond to
it, is documented in WAKEUP HELPCMS ...
snip
To make WAKEUP sleep all day, add a statement similar to this to your fil
e
of WAKEUP TIMES:
I'm not wholly comfortable with the :TLR implementation and the (then)
inevitable problem that VMARC would be generating archives that were
incompatible with older versions of VMARC (and, probably, VMAGUI -
something that I've just recently come to seriously appreciate).
I'd like to propose
Do you follow the IBMVM Discussion List? (In which case, if the
answer's, Yes you might reasonably expect them to have revised and
already know the answers to the other nine. :-) )
A couple of, matters arising that're otherwise apropos of nothing ...
Do people who survive on a diet of pizza
If you specify the HOLD option on your LOGOFF / DISC command:
LOGOFF HOLD
-- or --
DISC HOLD
do the symptoms change at all?
To quote from the HELP ...
HOld
causes the non-SNA TTY display terminal
and ... purely becasue I'm paranoid ...
IPL 190 CLEAR PARM SAVESYS CMS
Regards
jeff
it's hard for me to imagine developing a capability that
is to run in a VM/CMS environment that wouldn't involve PIPE at some poin
t
in the proceedings.)
Regards
Jeff Gribbin
returning control.)
Regards
Jeff Gribbin
, standalone environment, DDRing it would be equally
effective and removes the need to do the format/allocate - so, overall,
I'd suggest is unlikely to take much longer and leaves you with a simpler
process to execute because there will be no exceptions to handle.
Regards
Jeff Gribbin
It's been a while but, if I may, I think it's time to repeat my perennial
plea on behalf of those who, like me, have good reasons to access this
list in, Plain Daily Digest Mode.
When possible, could you PLEASE use Plain Text for your messages and
ESPECIALLY PLEASE, when possible, avoid
Regarding the, problem of perhaps wishing to only collect a subset of
the monitor records for, MONWRITE / post-processing activities while
still needing a fuller set of records for realtime monitoring, it is
really a trivial exercise to write a PIPE that collects MONITOR records (
a
la
with whatever locations ar
e
used by the loadlist or you'll end up building a new nucleus in storage
and then saving the wrong stuff into the NSS - a practice that can be the
source of some serious head-scratching until the penny (dime?) drops ...
Regards
Jeff Gribbin
that you didn't notice had happened and only discovered afterwards.
Hmm - I'm preaching again - does any of that help or am I off-target? (If
yes, please rephrase the question and I - plus many others, I'm sure g
-
will take another shot at it.)
Regards
Jeff Gribbin
The certificate makes a great background for your PC's desktop (I've been
using mine since about 30 minutes after I first discovered scanners). The
resolution's improved a bit over the years as scanner technology has move
d
forward. :-)
Congratulations and Welcome!
Sir Jeff the Builder of
If you have TRACK installed, that'll answer the question on an ad-hoc
basis without any further programming effort on your part. Otherwise, if
it were me and I were looking for a reliable, programmable interface I
reckon I'd be starting to think about writing an extension to QUERY ...
to achieve and then we can better advise you regarding what's
already, out there and what you might have to, roll yourself.
Regards,
Jeff Gribbin
I have had lots of experience with DDR - not recently, but I'm pretty
confident that this should still be accurate.
I've no experience pre-3330 and the following is written in a 3390 contex
t.
Assuming you're runnning DDR in a virtual machine and moving from and to
the same VIRTUAL cylinders
Chris Langford has already stated the fundamental answer to the original
question - I'll re-state it for emphasis before we fly off on too many
tangents and it gets lost:
To allow complete virtualisation of minidisks of any size up to and
including full-pack. Virtualising a full-pack
An Assembler Program That ABENDs ...
A little convoluted, and it would need a bit of wrap-round code to
generalise it and do things like verify load/start address, but it seems
that one could write an EXEC that effectively, HXd based on the
following ...
load dmsbtp
...)
Regards
Jeff Gribbin (Speaking only for himself.)
Ahah! Guess I just got lucky then! :-)
Looks like several nice features in there that I'm unlikely to ever get5
to use in anger.
Seen a GA date yet?
Alan / David / Adam,
Thanks for your responses - it would seem that my understanding of the
rules is not at odds with yours and that such a strategy is at least
acceptable from a legal / contractural standpoint.
Support of old DASD geometries was my specific thought - but I love the
idea of,
NO you can not run VM - any version - under
Hercules.
Now, this is one of those, But why would you want to do this? questions
,
but howabout running z/VM in a Hercules that was itself running under
Linux in a virtual machine that was being delivered using the same z/VM a
s
was running,
To save into CMS files, somebody would have to teach CP how to WRITE CMS
files - MUCH more challenging than its current ability to (simply) read
them. (SAVESYS needs to be a CP function - just because most SAVESYS
commands are executed within CMS doesn't mean that we can simply throw
away
).
Like others, I do wonder if the existence of a well-respected product tha
t
already does the job puts the damper on any further commercial developmen
t
of this capability inside IBM. Why reinvent the wheel where there are so
many other wheels crying out to be invented!
Regards
Jeff Gribbin
Unsurprisingly, it looks as if I need to clarify a little ...
Tom's not happy with, assuming R/R support for Reloc 0 Minidisks. My
take here is that CP is not unilaterally adding any R/R activity - if the
disk at Reloc 0 is a VSE minidisk and VSE doesn't issue any R/R then CP
won't either -
status on real packs tiresome - and it'd be so natural to assume shared
for XLINK packs.
OK, let's see what others think :-)
Regards
Jeff Gribbin
Somebody please pass me my hat - it's lunchtime.
I'm astonished and delighted.
Er ... meanwhile back at the original problem ...
Folks, Ed is reporting that EVERY attempt to issue CP IPL command to ANY
vdev is ALWAYS generating HCPCLS174E on a system that is otherwise runnin
g
happily. Now, sorry and all that, but I just don't buy the idea that thes
e
symptoms match
Hello Alan,
Seriously, what in your opinion are the odds that a problem with a paging
volume on a running system that's having NO OTHER paging problems could
produce the symptoms of ONLY and ALWAYS failing on IPL vdev?
Replacing paging volumes might be simple and easy but -given the symptoms
I've been sitting on my thumbs ever since this thread started, expecting
the, Ahah! post at any minute ... but it's not arrived.
If I'm reading the problem definition correctly we have a consistent,
repeatable problem - that alone makes me suspect that it's not a dodgy
chunk of pagespace.
On the, Get close to the application thread, remember that any I/O
request satisfied from MDC is likely to be satisfied (on modern boxes) in
less than a microsecond. Even cached, anything that involves a
conversation with a channel is going to experience a service time that is
several orders
(neither or) both volumes have the, magic volser to
(usually) milliseconds.
There's old sysprogs, and there's bold sysprogs ...
Regards
Jeff Gribbin
).
Regards
Jeff Gribbin
This really needs to be core VM function ...
David,
Let me reiterate that comment as I understand it, because I think it's
possible to interpret the scope of what you mean by, Core VM function i
n
different ways - and it's a definition that we need to agree upon if we'r
e
to have a fruitful
I recall how excited I was when I first learned about the *CCS support
mechanism that is used to support VTAM logon terminals in CP. The concept
of having an RDEVBLOK as the gateway to a server (didn't call 'em servers
back then - big mistake) opened up so many possibilities for device
This has now been resolved. MXG Update 24.035, available from Merrill,
addresses the problems.
Many thanks to all who contributed to identifying and resolving this
problem.
Regards
Jeff
91 matches
Mail list logo
