operating environment here is all z/os 1.13
how am i suppsed to clone and DISTRIBUTE (with emphasis on *distribute*) zfs
files?
CURRENTLY, I have a situation where 6 lpars, 3 production and 3 test, all share
the same master catalog. In that master catalog, the entry for OMVS.ROOT reads
as
Runtime Diagnostics is a point-in-time diagnostics tool that should be used
when you think there is something wrong on your system and don't know what it
could be or where you should start your investigation. It is invoked by F
HZR,ANALYZE (starting in R13) after it has been started. Prior to
In our older environment (no real sysplex), each system has its own master
catalog, but the root file system is part of sysres volume which is actually
shared between systems. We don't ship new copies of the root file system,
instead we IPL with a new version of sysres each month. The root file
I don't care that the user will look at the program logic. He is not
authorized to execute some of the commands in the program. The thing is
that I do not want the user to get control when the program run as they can
see run-time results of the program or even exit from the program.
I tried Russ
Itschak Mugzach imugz...@gmail.com wrote:
I don't care that the user will look at the program logic. He is not
authorized to execute some of the commands in the program. The thing is
that I do not want the user to get control when the program run as they can
see run-time results of the program or
You may not be able to create a VSAM dataset using a symbol for the volume
but after it is created you can alter the catalog entry to specify the
symbol.
Since you already have system symbols that contain unique values for each
system, why not add one more that specifies a unique qualifier for
In
90ec2e798a22854ebf67a14ec3fe093fa74f2ad...@scmbxc01.bcbad.state.sc.us,
on 10/26/2012
at 07:12 AM, Bonno, Tuco t...@cio.sc.gov said:
how am i suppsed to clone and DISTRIBUTE (with emphasis on
*distribute*) zfs files?
First set up youe wnvieonmwnr in accordance with z/OS UNIX System
Services
In 5089dd6d.8050...@valley.net, on 10/25/2012
at 08:46 PM, Gerhard Postpischil gerh...@valley.net said:
FSVO decades.
Decades meaning prior to 1979. My recollection is that SMC=SYSTEM was
dropped in the transition from OS/VS2 R1 (SVS) to OS/VS2 R2 (MVS), but
IAC see below.
It's in OS/390;
Hi
Thank you ,for your excellent answer
For me it would be interesting to get some notification
for example via ENF events if is something is wrong in the system
We are in z/OS 1.13, I will try to download the latest PTF's
On 26.10.2012 13:47, Karla Arndt wrote:
Runtime Diagnostics is
You mean like additional Health Checker alerts that can be reviewed from SDSF?
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Miklos Szigetvari
Sent: Friday, October 26, 2012 2:18 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Runtime
Certainly the version root is a way to go.
If you want to go another way, you can place the backups of the zfs files
on the res pack and restore them on the system where you want it cataloged.
Mount all the zfs's as read-only and you can share the zfs's as well as
the normal res pack.
Read-only
On 10/26/2012 12:31 PM, Shmuel Metz (Seymour J.) wrote:
Decades meaning prior to 1979. My recollection is that SMC=SYSTEM was
dropped in the transition from OS/VS2 R1 (SVS) to OS/VS2 R2 (MVS), but
IAC see below.
We ran SVS long after 1979, and jumped to MVS/SP; somehow I
overlooked or forgot
12 matches
Mail list logo
