You should be able to do this in REXX very easily (around 25 line EXEC). I
have tons of JCL where I read in a list (like the tape list) and the write out
the JCL. This comes from many years of laziness...
-Original Message-
From: IBM Mainframe Discussion List
Try this JCL:
//STEP1 EXEC PGM=IFCDIP00
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//SERERDS DD DSN=SYS1.LOGREC,UNIT=,VOL=SER=vv
Change the unit and volser and
Why don't you just backup the TMC? Surely you have a daily job that does this
- and it should clear the AUDIT file when it runs the backup from what I
remember.
From Quickref:
Action: Execute the backup program, TMSCOPY. All CA 1 utilities except
TMSCOPY and TMSINIT will abend with
We are in the same situation (on 1.9 and want to get to 1.12). After some
research I found that there was really no compat maintenance from 1.11 to 1.12,
so we just put on the compat maint for 1.9 to 1.10 and 1.9 to 1.11 and we're
currently trying the upgrade to 1.12. So far there have been
The main thing I have found that makes a good sysprog is the ability and drive
to not let a problem or issue beat you - that I will find the damn answer
drive that makes you always try and solve a problem. And you need to have
excellent problem solving skills.
I've found that good operators
What they have told me (in their usually secretive way) is that the IP address
for the HMC is listening for RIP announcements. They claim this could be a
security issue since a malicious intruder could send the HMC invalid RIP
announcements and give it bad routes. My response has basically
We still have some 3490 tape drives and I do remember using it sometime over
the last 10 years for a tape drive issue with the 3490's - per the CE request.
This is probably a good product to sunset and let users use it at their own
risk. I definitely would not spend any dollars testing and
I almost hate to give this answer, but the correct response to this is simply
IT DEPENDS. I have worked in a number of different shops, and your answer for
this depends greatly on the type of workload you have on the machine along with
expected/required level of performance and SLA's. At my
Don:
Thanks for the info - this corrected her issue. This was a new one for me...
C. Todd Burrell
PMP, MCSE 2003:Security
MCTS (640,642,643)
Security+, Network+
ITIL V3 Foundations
CSC Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM
I was going to go even further - why not just get rid of ML1 and add all of
those volumes to your primary storage groups? I think you will need one or two
ML1 volumes for VTOCs for backups, etc..., but I would get rid of the ML1
volumes to reduce cycles - and all migration would be straight to
If you have CA1 it could be an issue with your EDM setup, but I would think you
would have noticed this long ago. Have you tried to simply recycle the tape?
I would think this would force it to be freed up?
-Original Message-
From: IBM Mainframe Discussion List
not sure
how I could permanently fix this problem.
--- On Fri, 11/3/11, Burrell, C. Todd (CDC/OCOO/ITSO) (CTR) z...@cdc.gov
wrote:
From: Burrell, C. Todd (CDC/OCOO/ITSO) (CTR) z...@cdc.gov
Subject: Re: HSM ODDITY - NOT RELEASING EMPTY ML2 TAPES
To: IBM-MAIN@bama.ua.edu
Received: Friday, 11
You cannot run a batch job with the same name unless you logoff and back on to
allow the 8 character batch job to run. Thus, the 7 character userid allows an
extra character for batch job submission. I'm sure the UADS userid with the
'0' appended to the member name might have had something to
I'd probably just recommend that they run the start command after either
TCPIP or TSO. In our automation we have a number of tasks similar to
this one that we start after TCPIP (if it depends on TCPIP) or TSO.
C. Todd Burrell
PMP, MCSE 2003:Security
Security+, Network+
ITIL V3 Foundations
CSC
If you are at a DR site then the first thing I would look into is to
make sure that the IDMS SVC loaded properly when you ran CA90's to load
the SVC. Although normally SVC abends are SF**, this could possibly be
it. And if you do not have the proper LMP keys, this could also be an
issue. I
I think I made my regions something like 208K. I can edit pretty
much anything in TSO with this region size, and I run some very large
REXX execs that read in large files.
C. Todd Burrell
PMP, MCSE 2003:Security
Security+, Network+
ITIL V3 Foundations
CSC Lead z/OS Systems Programmer
Why not just put them under WLM control, and then the system controls
how many you use (up to your set limits)? This is much easier than
manually stopping and starting initiators, and it takes the control away
from operators who usually do not understand the impact starting too
many initiators
I do know that OPS can send emails, and we use it to send the emails to
our cell phones via a text message. Don't remember the actual process,
but I'm sure someone else can fill in that detail.
I believe that OPS requires a separate server and software to actually
do the calling out - we used
I would look into the functions that JES3 offers that JES2 does not
offer, and if you need any of these functions then go with JES3. But
unless you have a VERY compelling reason, then JES2 is probably the
better and easier to maintain option (IMHO). I've worked with both, and
JES3 can be
I would say that someone is doing a $T NUM command to reset this. We
used to have a command that reset it to 1 every week, but I saw no need
to continue this, so we stopped that practice. I say unless there is a
good reason to do it, I'd just let them roll around.
I do of another shop that
We have a small site and we used to upgrade yearly, but after awhile it
became too much of a hassle to constantly be testing and working on an
upgrade each year AND support all the ISV products and users as well.
Right now we try and do it every other year. To me this is up to each
site, but for
Your auditors are wrong (as usual). We do not require logons (except on
the HMC) as all of the consoles are in a secure room requiring card key
access. So there has never been a need for console logons.
I would definitely not call this an industry standard... If the
consoles are in a secure
In most small shops the need for extensive operator auditing and
security is not needed for accountability (IMHO). We normally have a
few operators on shift at one time, so if something happens on the
console we would be able to narrow it down fairly quickly. And we push
the use of SDSF for most
I think the valid question here is #3 - Why would you do that? I don't
know about everyone else on this forum, but I have too much to do to try
and get an operator fired in this way. And if you ever got caught doing
this, would you really want to lose your own job?
This has been an
For new JCL I always recommend just putting an ample region size on the job
card and be done with it. But I would certainly not change running JCL for no
reason.
I always say if it ain't broke don't break it.
C. Todd Burrell
PMP, MCSE 2003:Security
Security+, Network+
Lead z/OS Systems
When I first started at one job they talked about things called def-ism
and id-mmms. It took me awhile to figure out they were talking about
DFHSM and IDMS. And I also have heard someone use zoss instead of ZOS.
Of course this is the same shop that had RACF setup with single
character
I would add that this command should be done against your MASTER catalog
to get all aliases... This should show you all aliases along with their
associated user catalogs. Depending on your system this can be a
lengthy output.
If you remove the ALL parm you will get a list of all aliases only,
I seem to remember a couple of products that looked at all 12 characters in the
CPU serial number (I think they checked the actual hex machine code). These
products were a pain at DR with VM giving us a virtual 5 digit CPU. We usually
had to just get a temp key and the product worked.
I
We have ended up staying on Jobtrac 3.5 due to the horrible issues with
Jobtrac 11.0. We tried to upgrade a couple of times and ran into
catastrophic errors every time, so the decision was made to just stay on
an unsupported release than to try and debug 11.0 for CA. There were a
number of
We reached the point where I felt that all we were doing was debugging
Jobtrac 11.0 for the vendor. If the product is out on a beta release I
have no problem doing this, but we were on Jobtrac 11.0 SP3 and we were
still constantly sending in dumps to CA for different issues. We
eventually gave
Changing this to use the PARM actually seems to have fixed this issue.
Although I have no idea why this wouldn't work the other way? But I'll
incorporate this in the future.
Thanks for the tip.
C. Todd Burrell, PMP, MCP
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original
I'm on z/OS 1.9, and I ran a REPRO MERGECAT on one high level that had
over 225,000 entries, and it took a few hours on a weekend. I ran
separate jobs by second level, and ran about 500 separate jobs
single-threaded to get the job done.
I'd recommend just using REPRO MERGECAT during off hours
WLM inits have worked fine since around z/OS 1.5. So I would recommend
pushing back hard to get WLM inits running. Once you have them setup
your job will be much easier, because z/OS takes care of everything.
We had to tell our operators the same thing you need to tell your Prod
Control staff
If I had to choose one of these two, I would go with RMM. But CA1 is
probably the best (IMHO) mainframe tape management product. I would
rate RMM second... The only knock on RMM that I remember is that you
REALLY need to know REXX to use RMM.
C. Todd Burrell, PMP, MCP
Lead z/OS Systems
I would think that running these same procs over and over in the same
job would make the finders file pretty useless? I would think you
would want a second step to process the finders file, and then delete
it before creating a new one in the same job? Or just let the user
create the SORTOUT
Most of the time if I am not real sure, I just order both. The RECEIVE
process will ignore the extra PTF, so it's no big deal. IBM's
nomenclature can be very confusing.
C. Todd Burrell, PMP, MCP
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM
Why not just pick one of the larger high level qualifiers and move it to
another usercat, especially if the large high level is lightly used?
MERGECAT will move the high level, and then all you need to do is delete
and redefine the alias in all of the effected master catalogs. This
might buy you
I'm 43, and I have always been the baby every place I've worked (usually
by MANY years). Hard to believe I've been doing this work for 20 years.
C. Todd Burrell, PMP, MCP
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM Mainframe Discussion List
I'm pretty sure that you could do this type of search within a couple of simple
REXX members. I believe DCOLLECT might be able to give you all of the info
about all of the datasets on each TSO volume. Then it would simply be a matter
of pulling out the names of all of the PDS members for each
I have been trying to upgrade our Jobtrac 3.5 system to 11.0 for over a
year going through the various service packs up to SP3. I have yet to
have any success, and we finally gave up and decided to just run on 3.5
unsupported. Basically, 11.0 has been a piece of junk from day one, and
even on
I believe referenced usually means OPENED. I had a similar problem a
few years back when we IPL'ed a system that had not been down in about 6
months. HSM came up first, and deleted some files related to Netview.
C. Todd Burrell, PMP, MCP
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
I don't believe there is a VVDS on a volume if there is no VSAM, and if
the volume is non-SMS. So a sysres volume probably might not have a
VVDS on it, and most non-SMS volumes would not as well, unless there is
VSAM.
You could probably check for a VTOCIX if you make all of your volumes
have
If you have the space, just put this catalog on an empty volume, and
then dump/restore the whole volume using DFDSS or FDR. You could also
dump/restore just the dataset. You can also import/export using IDCAMS,
but I always find this to be a little trickier... I've run into some
issues with
If the tape is totally damaged and unreadable, then I would use the HSM backups
of the files on the ML2 tape to recover each dataset. There's a command to get
all of the files on the ML2 tape, and you can then HDELETE each dataset, and
then recover each dataset.
Once each file is recovered,
We don't have Java, but here's a couple of the mount points for our system:
MOUNT FILESYSTEM('OMVS.TST1.SHPHROOT')
MOUNTPOINT('/usr/lpp/php')
TYPE(HFS) MODE(RDWR)
MOUNT FILESYSTEM('OMVS.TST1.SHPEROOT')
Interogate the rest of the message for the ICD3009I return code and
reason code. If you look up IEC161I RC 040 in Quickref it states to
look into the IDC3009I return and reason codes that are in the remainder
of the IEC161I message.
Looks like something is amiss with a VSAM file?
Thanks
C.
Timothy:
Thanks for the response. This is exaclty the type of into I am looking
for. We are pretty tied to try and use a solution from CA since we have
a global license there and we are trying to replacing a cost product
with a solution that is free, thus giving us cost savings. But I'll
look
I had heard about the requirement to go to R11, so I ordered it about
8-9 months ago and tried to install it. It was a TOTAL piece of junk
(numerous abends and MANY PTF's needing to be installed). CA finally
told me to install the latest PTF tape, and that would fix all of the
problems. But the
We've been up on 1.9 in production for a few months, and I've seen no
XMITIP issues at all.
C. Todd Burrell
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Richbourg, Claude
Sent:
Wouldn't a F13 abend indicate that the '13' is HEX, so this is actually
SVC 19 (OPEN)? This would make a LOT more sense...
C. Todd Burrell
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
I had the same types of issues with SDSF when I went to 1.9, and I found
that the main slow issue was with the HELD queue display. OUTPUT was
also slow. My work around was to simply reduce the number of days of
output in the queue, and more aggressively pull output to CA-View. It
seems that
We generally create a dataset with the low level qualifier of OUTPUT
and keep all of the job output from a product's installation in that
PDS, and we try to name the members something meaningful (like the
install doc name of the job submitted). We also have CA-View, and I
also keep the output
I wanted to reply back and thank everyone for their responses. I was
finally able to get this to work, and the email below really triggered
the solution. What was really puzzling was that Tapemap could read the
tape, but I was having trouble getting anything off of the tape with
ICEGENER,
The CE did have to make a visit yesterday for some issue with the
3420's. But it could not have been too much of a problem since he was
gone in about 30 minutes...
C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(770) 917-8081 (home)
(404) 723-2017 (cell)
Please visit the ITSO Customer
I tracked down the Service unit to CPU second conversion constants in
the Init and Tuning Guide. This is what I need, because I have the SU's
already from the type 30 SMF records. Once I put in the coefficients, I
should have a good number.
Thanks to everyone that replied. It had just been
I appreciate all of the replies. As I had figured, we're pretty much
out of luck right now. We're going to try and figure out a way to get
on a 3420 that can read 800 BPI, but we may still have an issue with OS
releases, etc... We were trying to help out one of our customers, and
this turned
Try typing the command SET DISPLAY ON on your SDSF command line. You
probably have something set like DEST or OWNER, and you can turn these
off with OWNER or DEST commands.
C. Todd Burrell
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM Mainframe
From the 1.9 manuals:
54
Explanation: DELETE failed because the data set is being renamed but it
has not completed.
Programmer Response: Rename the data set with the IDCAMS ALTER command
and then delete it.
There were vertical bars beside this entry, so it was added via PTF
after the manual
I think when we used to use Netview that Netview came up before VTAM, so
this would explain the messages. I believe that Netview should come up
first from what I remember.
C. Todd Burrell
Lead z/OS Systems Programmer
ITSO
(404) 723-2017 (Cell)
-Original Message-
From: IBM Mainframe
I would simply change the ENTRIES line to say LEVEL, and then run this.
Once you copy the entries, then you need to quickly define the alias.
Here's a sample job I've run to move aliases that mistakenly made it
into the master catalog:
//MERGC1 EXEC PGM=IDCAMS,REGION=0M
I would say somewhere between 5 and 10 years experience depending on
what and where the experience occurred. I worked in a sweatshop for my
first 8 years, and probably got 20 good years of experience there. But
some people spend their first 5-10 years only installing a couple of OEM
products, so
We are currently on 1.8, and I am working on the 1.9 upgrade right now.
Due to MANY issues with IDCAMS with 1.8, I'd just go to 1.9. It appears
that many of the LISTCAT issues with IDCAMS were fixed in 1.9. There
were many quirks in LISTCAT in 1.8 that made it a pain to deal with...
C. Todd
It's been MANY years since I worked with Zeke, but I remember that it
had some nice batch utilities where you could pull things off the
schedule and add them back. So you should be able to pull off all the K
jobs, edit the input, and then put the jobs back out there as Z jobs.
You may need to do
One of the biggest things we have done is to move as much as possible
from tape to disk. We had a large number of batch jobs at night that
used tape, and some of the jobs used the SAME tape as input. Moving
these files to disk probably cut down the nightly batch cycle by around
20 percent
We converted here at CDC about 2 years ago because we were down to
around 50 users on Roscoe, and we could not justify the cost. I was
able to write a job to pull all of the Roscoe libraries over to PDS's,
and I assisted the users in rewriting their RPF's to REXX execs.
Unfortunately, it was a
I don't think there is any way to do real time duplexing of the SMF
(SYS1.MANx files) as they are written. However, we offload our SMF data
hourly during the day, and send the output to two separate output files
appending the data to the end of the files. Then we pull the data on a
daily basis
I'd recommend re-checking the volume definitions for the master catalog
your are trying to use, just to verify that everything looks good with
the PAGE datasets. Then re-verify your correct LOAD parm address and
LOADxx member, and be sure you're not using a different SYSx.IPLPARM
than you think
Our high level of OMVS has been in a user catalog for quite awhile with
no issues. I always rename the OMVS.ROOT and other OMVS datasets that
come with a Serverpac to be something like OMVS.ZOS180.ROOT (for z/OS
1.8), so this keeps me out of a duplicate dataset situation. Otherwise,
I have run
That was it. I have not done or looked at COBOL in a LONG time, so I
was not sure where to look. Not I have to figure out who changed this
to not work, but that's my cross to bear.
Thanks for the quick help.
C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(404) 498-3299
(404) 723-2017
This may be a stupid suggestion, but why not just restore the data to
spare volume(s), and then recreate the dump on disk with the same
dataset name as the current tape (rerun the dump)? Since the COPYDUMP
command does not seem to be a good option, I'd just try to recreate the
dump in another
A wild guess would be that these are related to a CA product called
Roscoe. I think Roscoe has two releases of 5.7 and 6.0, and these look
familiar.
C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(404) 498-3299
(404) 723-2017 (cell)
-Original Message-
From: IBM Mainframe
were running Roscoe for releases 5.7 and 6.0. These would need to be
defined to TSS or RACF.
C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(404) 498-3299
(404) 723-2017 (cell)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Burrell, C
I think the new releases are supposed to be annually released every
September 30th?
C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(404) 498-3299
(404) 723-2017 (cell)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mark Steely
Sent:
We've got 1.8 on our test system, and I tested this out, and I do not
see the same problem. It seems to work fine on our 1.8 test LPAR.
C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(404) 498-3299
(404) 723-2017 (cell)
-Original Message-
From: IBM Mainframe Discussion List
You should be able to send the SYSPRINT DD to a dataset, and then you
can use whatever programming language you want to look at this file and
pull out the dataset names that were successful, and not successful. I
recommend REXX, but you can probably do this with almost any language.
C. Todd
I believe the Ranade series had an MVS Control Blocks book. This was an
excellent resource for how the main control blocks for MVS were related.
With that and the Data Areas manuals you should have a good start.
Don't know where you can track down a Ranade book, but you should be
able to find one
You can put SJ beside the job and edit the JCL.
C. Todd Burrell
Senior z/OS Systems Programmer
ITSO
(404) 498-3299
(404) 723-2017 (cell)
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Rugen, Len
Sent: Friday, February 24, 2006 10:08 AM
You can also use DFDSS DUMP with the wild carding and the DELETE option
with a dummied output. I like this because you can run it with
PARM='TYPRUN=NORUN' to have a 'practice' run to see what it will
actually delete.
You can also use this to make a backup of the 'to be deleted' files.
C.
I have both copies of this book (the older blue slim book and the newer brown
and white thick book). If you are talking about the older version, then I
would be glad to sell it to you. I don't need both copies, but I would like to
keep the second edition.
Email me directly at [EMAIL
This is a good example of this without a job card. The BY operand for
this one hits uncatalogued datasets on a particular volume that are more
than two days old, but you can get rid of the BY operand and just use
INCLUDE and EXCLUDE. I ALWAYS recommend running with TYPRUN=NORUN first
just in
80 matches
Mail list logo
