HDEL in front of each dataset name, instead of D.
Type HDEL on the first one, = on the rest.
DSLIST is smart enough to recognize when a data set is migrated. It will issue
HDELETE
in the background.
--
Peter Hunkeler
--
For
HDEL doesn't have the option of confirming each dataset. And I don't
like to turn off the confirmation.
On Fri, Feb 21, 2014 at 2:21 AM, Hunkeler, Peter
peter.hunke...@credit-suisse.com wrote:
HDEL in front of each dataset name, instead of D.
Type HDEL on the first one, = on the rest.
DSLIST
Paul Gilmartin wrote:
Often, after finishing a series of tests, I have several dozen data sets to
delete. Actually, I'm careless; often I don't delete them until the next time
I want to run similar tests, by which time most are migrated.
Others made good suggestions, but I believe my
On Fri, 21 Feb 2014 03:16:19 -0600, Elardus Engelbrecht
elardus.engelbre...@sita.co.za wrote:
Thanks for writing this. I couldn't find it anywhere although I knew it
existed...It now exists in my list of notes of things not to forget, ever!
Why? Use //D before first DSN and // at last one in
HDEL doesn't have the option of confirming each dataset. And I don't
like to turn off the confirmation.
I didn't say you should use HDEL. I said DSLIST will issue an HDEL if the data
set is migrated. It does so only after the confirmation prompt, if you have
delete confirmation on. BTW, in
Sebastian Welton wrote:
Thanks for writing this. I couldn't find it anywhere although I knew it
existed...It now exists in my list of notes of things not to forget, ever!
You're most welcome! It was my pleasure to be able to help you.
Just don't forget to remember to preserve that list of
I agree on both points--if there's a requirement it should be documented, and
we don't have any MIH values coded for our DS8870. We still have some in there
for tape, which I think is still recommended even with the TS7700 VTSes.
I do recall in the past having to put in temporary MIH values for
Hi, List,
Running z/OS 1.13 and DB2 v10 (conversion mode). In preparation for
Enterprise COBOL v5.1 we are converting load libraries from PDS to PDSE. Our
DBAs have found ONE (so far) DB2 Stored Procedure that runs correctly if loaded
from a PDS, but suffers an Abend S0C2 if loaded from a
Steve Thompson wrote:
You probably want to look at DFSMS Using Data Sets. The one that I will be
referencing is SC26-7410-11.
Page 553 has a title Using the POINT Macro to Position to a Block
Thanks for getting to the POINT. ;-D
Now I know POINT is described there, not in POPs as described
In 5304bab0.9010...@charter.net, on 02/19/2014
at 09:07 AM, Gerhard Postpischil gerha...@charter.net said:
I think we have way to many instructions already g
Had IBM defined a real byte-oriented[1] architecture, some of those
instructions would not have been necessary.
[1] On the 7030, you
In 2459250746283941.wa.paulgboulderaim@listserv.ua.edu, on
02/19/2014
at 09:10 AM, Paul Gilmartin paulgboul...@aim.com said:
ObQoheleth?
Indeed, for there is nothing new under the Sun.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
In 922356206.5038169.1392826350263.javamail.r...@comcast.net, on
02/19/2014
at 04:12 PM, DASDBILL2 dasdbi...@comcast.net said:
You're right. I had forgotten about the S/360 model 67. Most of the
360s in production were not model 67s, however. Certainly all the
360s which I knew anything
In
caarmm9sghyf0y5+jwzsc27wpt967weqyyohia8rz0odkv-n...@mail.gmail.com,
on 02/19/2014
at 12:29 PM, Tony Harminc t...@harminc.net said:
In my circles the term core survived for quite a long time after
the introduction of the first 370 models with non magnetic-core
storage (the 158 and 168,
The
In
caarmm9rzepkzt2z1eb2rqcjxeildu75-9bxjbkeech++ay1...@mail.gmail.com,
on 02/19/2014
at 02:43 PM, Tony Harminc t...@harminc.net said:
No what?
No, that is not how conditional branching in channel programs has
always worked.
I think we need a counter for your yearly use of this cliché,
I
In 0544414971930445.wa.david.speakebcbssc@listserv.ua.edu, on
02/19/2014
at 04:56 PM, David Speake david.spe...@bcbssc.com said:
Can anyone tell me how the BSAM POINT macro works for tape.
What kind of tape? For open reel, the access method had to count
blocks. I don't know for sure
In 785217.3535...@smtp203.mail.ne1.yahoo.com, on 02/20/2014
at 05:05 PM, Scott Ford scott_j_f...@yahoo.com said:
X-MIME-Autoconverted: from base64 to 8bit by jefferson.patriot.net id
s1KE6kSq009730
That's inserted by my provider.
guys is this message better and not base-64-encoded ???
Based
Ant,
Is DF/DSS smart enough to notice that if I am sending the output to DD DUMMY to
not recall HSM migrated datasets before deleting them?
Rex
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Anthony Thompson
Sent: Thursday,
Have you verified the difference in terms of APF authorization between
the two libraries and the two runs ?
Sometimes it happens. You can loose APF Auth if you load a module from
LNKLST or not .
Hope this can help.
Best regards.
Massimo
2014-02-21 14:18 GMT+01:00 Chase, John
Skip,
To answer your original question, No, prior to v2r1 (and being in distributed
mode) there is no way to add an MCS console without an IPL.
I also don't know of any system command that will show you that a console
device is pinned. Note that any device you've specified in CONSOLxx as a
W dniu 2014-02-21 14:43, Pommier, Rex pisze:
Ant,
Is DF/DSS smart enough to notice that if I am sending the output to DD DUMMY to
not recall HSM migrated datasets before deleting them?
AFAIK, DSS does not touch migrated datasets. It doesn't matter whether
you want to dump it to real dataset
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Massimo Biancucci
Have you verified the difference in terms of APF authorization between the
two libraries and the two
runs ?
Sometimes it happens. You can loose APF Auth if you load a module from LNKLST
or
Re-bind the procedure?
snip
Running z/OS 1.13 and DB2 v10 (conversion mode). In preparation
for Enterprise COBOL v5.1 we are converting load libraries from PDS to PDSE.
Our DBAs have found ONE (so far) DB2 Stored Procedure that runs
correctly if loaded from a PDS, but suffers an Abend
Peter Fatzinger wrote:
I also don't know of any system command that will show you that a console
device is pinned. Note that any device you've specified in CONSOLxx as a
console will be pinned.
Just curious, [1] how do you know in the first place a console device is
'pinned'?
Thanks in
For IEFBR14 two things:
#1. I constantly use; DISP=(MOD,DELETE), so if the data set exists; it will be
allocated and then deleted, but if the data set does not exist; it will be
created and then deleted. I use SPACE=(TRK,(0)) in the IEFBR14 step for a data
set that I will later define with
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of R.S.
Sent: Friday, February 21, 2014 8:07 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Deleting multiple data sets
W dniu 2014-02-21 14:43, Pommier, Rex pisze:
Ant,
Is DF/DSS smart
The DBA who first encountered the problem informs me that it is a plain old
Assembler application, and NOT a Stored Procedure.
The rest of the symptoms and questions remain as originally stated.
-jc-
snip
Running z/OS 1.13 and DB2 v10 (conversion mode). In preparation
for
On Fri, 21 Feb 2014 14:36:10 +, Chase, John jch...@ussco.com wrote:
The DBA who first encountered the problem informs me that it is a plain old
Assembler application, and NOT a Stored Procedure.
The rest of the symptoms and questions remain as originally stated.
Hi John,
My guess is that
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Doug Henry
On Fri, 21 Feb 2014 14:36:10 +, Chase, John jch...@ussco.com wrote:
The DBA who first encountered the problem informs me that it is a plain old
Assembler application,
and NOT a Stored Procedure.
My question would be when was it last assembled and lnked? It is possible it
needs to be assembled and link with newer modules?
Is it code 24bit or 31bit?
Is it using STOW or POINT functions?
These are just guesses, but maybe it is trying to access a member using very
specific PDS functions
As for the message, during IODF ACTIVATE (including TEST), you get this
message:
REASON=0151,CAN NOT DELETE DEVICE
DESCTEXT=DEVICE PINNED, ASID = 0001
DEVICE IN USE AS A CONSOLE
COMPID=SC1CK
While combing the web yesterday, I came across APAR OA33088 (2010) which
Hi, we have a mainframe dataset that is used daily used in our automated
scheduling processes.
Occassionally, our ops support gets paged out because a process is delayed
and it turns out it was because
said dataset was migrated and had to be recalled.
this dataset's management class has nolimit
We have an SMS management class which stops that. It does it by setting the
CMD/AUTO MIGRATE to NONE.
On Fri, Feb 21, 2014 at 10:15 AM, Michael Bieganski
mbiegans...@gmail.comwrote:
Hi, we have a mainframe dataset that is used daily used in our automated
scheduling processes.
Occassionally,
Michael,
For a quick fix, do you have any of the more popular JCL management tools? If
so, there is a way to always ensure the dataset is allocated and available
before the initial access from your production processing hits it for the first
time.
Mitch
-Original Message-
From:
Is it possible someone might be manually migrating the file?
I would run a PDA report for the file and see what information has been
collected. Info on it can be found in the z/OS V1R12.0 DFSMShsm Diagnosis
GC52-1083
I have found this process very helpful.
Second, if you have the CBTTAPE.ORG
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Lizette Koehler
My question would be when was it last assembled and lnked?
Date in the load module / program object is 2010.322.
It is possible it needs to be assembled and link with newer modules?
I'll suggest
We occasionally have the same problem. Nothing worse than seeing
Automation wait for a recall. My take is to put such IPL-critical data
sets on a volume not subject to migration at all. We have on every plex a
handful of SYSxxx packs that are not SMS managed. Any data set that is
crucial to
Attempting to build a new IOCDSA0 but getting the error below. According to
msg ICP408I to correct this issue ' use Disable Write Protection under Options
on the Input/Output Configuration panel' but exactly where is that and how do I
change it? Thanks Matt
The current activation profile on
You need to go to HMC select Single Object, look for Input Output
Prrogam, select slot A0 and unprotect it
Carlos Bodra
IBM Certified Specialist System z
Sao Paulo - Brazil
Em 21/02/2014 14:24, Dazzo, Matt escreveu:
Attempting to build a new IOCDSA0 but getting the error below.
In the HCD diaslogs, select 2, then 11 then S and then put a / against the
A0. It will give you choices. I forget which one E or W I think will
remove the write protect.
Alan Field
Technical Engineer Principal
BCBS Minnesota
Phone: 651.662.3546 Mobile: 651.428.8826
From: Dazzo, Matt
Dazzo, Matt wrote:
Attempting to build a new IOCDSA0 but getting the error below. According to
msg ICP408I to correct this issue ' use Disable Write Protection under
Options on the Input/Output Configuration panel' but exactly where is that and
how do I change it? Thanks Matt
The current
The private area size can be displayed by this TSO TEST command:
L 224.%+30?+40
7FF16E50. 007FA000
The result, hex 007FA000, varies of course from system to system.
This is the same field, LDASIZA, shown by the IPLINFO exec.
I assembled variations of a 24-bit program with different sizes and
Thanks, should have checked the archives first. How would an IOCDS get write
protected other than a manual process? Thanks
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Elardus Engelbrecht
Sent: Friday, February 21, 2014 12:51 PM
I believe that an actual POR sets the flag, but most people don't POR very
often.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com
From: Dazzo, Matt
W dniu 2014-02-21 19:36, Skip Robinson pisze:
I believe that an actual POR sets the flag, but most people don't POR very
often.
Yes, POR set write protection on IOCDS.
User also can set it, but IMHO POR is the most typical reason. Last, but
not least: not many persons shoud have access to
In the interest of avoiding foot shooting, IMO, your current active IOCDS
should always be write protected.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Dazzo, Matt
Sent: Friday, February 21, 2014 10:30 AM
To:
W dniu 2014-02-21 20:17, Gibney, Dave pisze:
In the interest of avoiding foot shooting, IMO, your current active IOCDS
should always be write protected.
Yes, but it's important to know what is current active IOCDS. If you
performed POR month ago and no changes in HCD/IODF were made, then it's
the first thing to check would be entry point - a non-zero entry point is
one of the easiest things to loose in a LKED.
On Fri, Feb 21, 2014 at 10:37 AM, Chase, John jch...@ussco.com wrote:
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Lizette Koehler
My
You wrote:
In such case one should write new IOCDS from current IODF file.
Always, then switch it to active in the HCD dialog after activating the
IODF. That write protects it. I'm fairly certain that releases write
protect on the last one.
Thomas Ambros
Operating Systems and Connectivity
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Mike Bell
the first thing to check would be entry point - a non-zero entry point is one
of the easiest things to
loose in a LKED.
ENTRY_POINT = LOAD_POINT, but the DB2 interface was the first CSECT in the load
Zap an 0C1 into the PDS version at the MVCK. I bet you will find the module
loaded into a different storage area with different attributes.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU]
On Behalf Of Chase, John
Sent: Friday, February 21,
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Gibney, Dave
Zap an 0C1 into the PDS version at the MVCK. I bet you will find the module
loaded into a different
storage area with different attributes.
It appears from our tentative diagnosis that the MVCK
(did I mention the Pioneer 10 response time issues viz the daily digest, yet?
*grin*)
So, Willie, an additional verification is Does DISPLAY SMS give IGD002I ...
SCDS = SYS2.SMS.SCDS? Also, does ISMF display the same DataClas information
for CDS Name: 'ACTIVE'?
If IGD002I gives a different
Again, daily digest delay caveat insert...
Gil: once in DsList, use sort on any two columns ie. SORT DSORG VOLUME. Then
you can move to your grouped clusters (Vol= *VSAM*) for D line commands
followed by the Migrate Volumes (Vol=Migrat*) for HDelete. Unfortunately, (in
v1.12 anyway), it
On 20 February 2014 21:40, Shmuel Metz (Seymour J.)
shmuel+ibm-m...@patriot.net wrote:
on 02/19/2014 at 02:43 PM, Tony Harminc t...@harminc.net said:
I didn't suggest, let alone say, anything counter to this.
Then who wrote Indeed this is the way conditional execution and
branching works (and
I confess to not having digested every post in this thread, but some
additional (or restated) observations:
1. For 'a long time now', simple 'd' on a DSLIST is converted
automatically to HDELETE for migrated data sets. And nothing gets recalled
in the process. I just tested this. 'del' is not
In:
http://pic.dhe.ibm.com/infocenter/zos/v2r1/topic/com.ibm.zos.v2r1.gim3000/gim3161.htm
I read:
Coexistence considerations
SMP/E for z/OS User's Guide
SA23-2277-00
SMP/E releases before V3R5 cannot process the MCS input that is developed
specifically for V3R5, nor can they process
On 21 February 2014 11:37, Chase, John jch...@ussco.com wrote:
Browsing the dumped storage around the program's load address (x'7000') I
see:
Event 1 CSECT DBR915B0 GPR 15 (Address 7000)
700080ECD00C*..}.*
On 21 February 2014 15:28, Chase, John jch...@ussco.com wrote:
It appears from our tentative diagnosis that the MVCK instruction was not
in executable code, but rather was just data
in the PARM passed to the program at invocation. Thus the questions about
where the system places PARM data
Update on the console saga. Of the three sysplexed SDM (XRC) systems on
the CEC in question, one is easily expendable. So I ran IEARELCN on the
skinny stepchild to remove 10 offending PINNED consoles. It was pointed
out afterwards by a colleague that in a sysplex, removing a console
affects
There was toleration support in SMP/E 3.4 for FIXCAT holddata, but it was to
ignore it, not to process it. Note that GIM58903W does not show up in QuickRef
until SMP/E 3.5. I don't recall the PTF# for toleration. It was in the 2008
timeframe.
You also may need to run the upgrade command in
60 matches
Mail list logo
