Thanks, Dave, I thought it was something like that.
Cheers
-Robin
-Original Message-
From: Dave Cole [mailto:dbc...@gmail.com]
Sent: 27 August 2013 21:54
To: IBM Mainframe Discussion List
Cc: Robin Atwood; Bob Shimizu; Calin Cole
Subject: Re: XDC-CDF cannot access profile
Hi Robin,
On 8/27/2013 5:57 PM, Shriver, Gregory A wrote:
Another possible resource that helped me was to sit down with a cup o joe and
inspect the resulting SYSTRACE line by line. And review the LOGREC as this
will provide evidence of the actions of all recovery routines for which
RECORD=YES was
Hi,
Is there a way to find out which jobs userids was Holding/Locking the dataset?
One of our FTP job failed in July and need to find out the root cause of the
failure. We have not seen any network failure, so need to find out anyone was
holding the dataset during that time.
Regards,
SMF record type 77. There's also SMF type 14/15's, but they won't say if the
file was only allocated and not opened.
Ant.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Chokalingam Thangavelu
Sent: Wednesday, 28 August 2013 5:59 PM
Chokalingam Thangavelu wrote:
Is there a way to find out which jobs userids was Holding/Locking the
dataset?
If *during* the event, you can try renaming a dataset and then use PF01 in TSO
/ ISPF or try on console this command:
D GRS,C to see any contention.
Or have your automation product
If FTP does an ENQ,RET=TEST, determines that the dataset is not available and
terminates the transfer, there is no contention to display.
You can do a D GRS,RES=(*,dsname) to see who is holding the dataset at that
moment.
Kees.
-Original Message-
From: IBM Mainframe Discussion List
Vernooij, CP - SPLXM wrote:
If FTP does an ENQ,RET=TEST, determines that the dataset is not available and
terminates the transfer, there is no contention to display.
Thanks, I know that. This is why I posted alternatives and why I asked what
messages are there.
You can do a D
We are looking at replacing our 3594 tape library. Even after reading
loads of manuals, I am unsure if I could use LTO 5 cartridges in 3584
tape library or would I have to use 3592-E05.
Are LTO 5/6 just treated as a different media type ?
Crispin Hugo
Systems Programmer
Macro 4 Limited
There are many ways to determine the contention with a dataset.. As you
have already got an examples with above replies.. The best way to determine
is with D GRS,C or D GRS,RES=(*,dsname in question) or if u r in ispf panel
3.4 option press F1 twice having the dsn in question listed
On Aug 28,
On Wed, 28 Aug 2013 08:28:31 +, Chokalingam Thangavelu wrote:
Is there a way to find out which jobs userids was Holding/Locking the
dataset?
One of our FTP job failed in July and need to find out the root cause of the
failure. We have not seen any network failure, so need to find out
W dniu 2013-08-28 13:11, Crispin Hugo pisze:
We are looking at replacing our 3594 tape library. Even after reading
loads of manuals, I am unsure if I could use LTO 5 cartridges in 3584
tape library or would I have to use 3592-E05.
Are LTO 5/6 just treated as a different media type ?
send email
The best principle is the principle of least astonishment - it is best to
not dictate from on high.
If this is new API, allow for a RC parameter, which, if not specified, leads
to an exception.
If this is a new plug-in for an existing API, you are stuck with the previous
results.
On Tue, 27 Aug
Thanks Radoslaw, just what I needed to know.
Crispin Hugo
Systems Programmer
Macro 4 Limited
Direct Line: +44 (0)1293 872121, Switchboard: +44 (0)1293 872000, Fax: +44
(0)1293 872001, Mobile: +44(0) 7753951308
A Division of the UNICOM Global
www.macro4.com
Macro 4 Registered
Ed,
I couldn't help commenting I am still learning ...even after my coffee !
Scott ford
www.identityforge.com
from my IPAD
'Infinite wisdom through infinite means'
On Aug 28, 2013, at 2:19 AM, Ed Jaffe edja...@phoenixsoftware.com wrote:
On 8/27/2013 5:57 PM, Shriver, Gregory A wrote:
Miklos,
This is exactly what I was looking forBig Thanks
Respectfully,
Willie C. Rouse
Senior Mainframe Consultant
Prince George's County, Maryland
Office of Information Technology
9201 Basil Court/ Room B8
Largo, MD 20774
Voice: 301-883-7189
Fax: 301-883-3790
-Original Message-
I recommend that you use the PAUSE/RELEASE pair instead of WAIT/POST.
The WAIT/POST pair is, like GETMAIN/FREEMAIN, lumbered with the
detritus of the ages, much of it ugly.
Let me also add that another important, in some contexts crucial, use
of subtasks stems from the fact that failures within
A recovery routine cannot change SDWACLUP (or most of the fields in the
SDWA) and have such a change be useful to anything. If you are intended to
change it, usually SETRP will let you do so, or it's a field relevant to
retry or it's one of the communication fields. SDWACLUP is on not only
for
Since you are looking to go back in time, it may or may not be valid to do a
D GRS,RES=(*,datasetname) in SDSF or Console.
However, if you still have the SMF data, there is a utility on the
www.cbttape.org called DAF.
This can read your SMF data and by just using DSN EQ datasetname
You may find
And one thing to remember is that the main task, in the PAUSE/RESUME or
WAIT/POST must poll for communications from the subtask. I have not used
PAUSE/RELEASE, but it appears that, unlike WAIT/POST, the task doesn't have
a way to poll to see if something has sent a message. I.e. when the main
task
Peter, thanks, no the IBM documentation is not confusing. The concepts are
somewhat complex, and I have not written any ESTAE code in nearly twenty
years. I get it now, I think.
The problem is the intersection of what I want to do, what MVS wants to do,
and what LE wants to do. We are in some
John,
Just to be complete, there is a TEST_PAUSE function, which while not as fast as
a TM of an ECB, it does provide the polling function you described.
When using queues, the polling function is to test if there is anything on
the queue, only when there is nothing on the queue do you go into
Thanks. Must have missed than in my quick perusal of TFM.
On Wed, Aug 28, 2013 at 9:37 AM, Blaicher, Christopher Y.
cblaic...@syncsort.com wrote:
John,
Just to be complete, there is a TEST_PAUSE function, which while not as
fast as a TM of an ECB, it does provide the polling function you
Rather than rely on task structure to limit failure damage, each task should
establish its own recovery environment and pass back a return code via some
non-destructive way.
Recovery processing is also covered in the Assembly Services Guide and the
Authorized Assembly Services Guide.
Scott,
On 2013-08-28 09:53, John McKown wrote:
And one thing to remember is that the main task, in the PAUSE/RESUME or
WAIT/POST must poll for communications from the subtask. I have not used
PAUSE/RELEASE, but it appears that, unlike WAIT/POST, the task doesn't have
a way to poll to see if something
I am trying to get an ESTAEX recovery routine to call an LE C routine. Why?
I want to do some diagnosis and cleanup following an ABEND. Why not use LE
conditions and/or C signals? I do, but LE's ESTAE(X) is (apparently) TERM=NO
and does not catch certain ABENDs such as operator cancel. Why cancel
I rarely use TERM=YES. I use RTM exits almost exclusively for error
reporting and setting a retry. About the only time TERM=YES is used is in
the primary driver task for a cross memory server so that its RTM exit can
reset the PC services available flag to minimize D6 abends. But I don't even
rely
This is just a question.
Have you looked at using a LE User Handled Condition instead of an ESTAEX?
CEEHDLR-Register User-written condition handler
z/OS V1R12.0 Language Environment Programming Reference
SA22-7562-12
CEEHDLR registers a user-written condition handler for the current stack
As Chris Blaicher and Sam Siegel have suggested, PAUSE/RELEASE is
logically complete. Anything that can be accomplished with WAIT/POST
can be accomplished, more elegantly and with fewer barred windows and
culs de sac, with PAUSE/RELEASE.
As Chris mentioned, intertask communication can be
Chris Blaicher wrote:
begin extract
Rather than rely on task structure to limit failure damage, each task
should establish its own recovery environment and pass back a return
code via some non-destructive way.
/end extract
and I suspect that we disagree sharply about this. That tasks should
Thank you to the always-helpful Lizette!
Yes, I have looked at a lot of things. You know how these things are: you
head down one path, you hit some negative, so you head down some other path,
and then you hit some new negative, so perhaps you go back to the first path
...
From the LE P/G,
On 8/28/2013 8:03 AM, John Gilmore wrote:
As Chris Blaicher and Sam Siegel have suggested, PAUSE/RELEASE is
logically complete. Anything that can be accomplished with WAIT/POST
can be accomplished, more elegantly and with fewer barred windows and
culs de sac, with PAUSE/RELEASE.
Logically
I agree and disagree with John. I do have lots of places in code I have
written that die a very ugly death at the point I get to an illogical situation
because I do want to see what is going on at that instant.
In other cases, such as data exceptions, I swallow the error and send back a
On Tue, 27 Aug 2013 19:48:25 -0400, Blaicher, Christopher Y. wrote:
There are lots of ways to do this. Some of the questions you have to first
ask are: 1) Are the tasks asynchronous to each other? 2) Can there be more
than one slave task? 3) What are you attempting to accomplish with sub
If your company is interested in doing this sort of benchmarking on a regular
basis, or having access to analysis and benchmarks outside of IBM I suggest you
look into the PAI/O Driver from Performance Associates.
Ron
-Original Message-
From: IBM Mainframe Discussion List
This will report onb GDG's with no GDS's attached. You could alter it to also
delete them if you want.
JCL:
//LISTCAT EXEC PGM=IDCAMS
//SYSPRINT DD DSN=amp;SYSPRINT,
// SPACE=(CYL,(50,20),RLSE),
From the confirmation screen:
The information you provide will be used to validate your entitlement and
communicate with you about your service requests.
Name Dave Gibney
E-mail address gib...@wsu.edu
How should customer support contact you about this service request?
Preferred contact method
This beautiful example is gilding the lily. Why not just delete all the
GDG bases? Lots of CC8(12?) but hold your nose and it's done.
On 8/28/2013 1:18 PM, Greg Dorner wrote:
This will report onb GDG's with no GDS's attached. You could alter it to also
delete them if you want.
JCL:
Some organizations require datasets being deleted, not of your uid, be listed
in advance, documented and done via change ticket.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of Tony Babonas
Sent: Wednesday, August 28, 2013
Probably not old enough to have ordered anything online before
In a message dated 08/28/13 13:27:47 Central Daylight Time, gib...@wsu.edu
writes:
The information you provide will be used to validate your entitlement and
communicate with you about your service requests.
In lcrr19p9rbgguhn83c09ae4cjv3i0km...@4ax.com, on 08/28/2013
at 03:33 PM, Binyamin Dissen bdis...@dissensoftware.com said:
The best principle is the principle of least astonishment - it is
best to not dictate from on high.
That requires a knowledge of the local culture. For COBOL an exception
In
cae1xxdeh6qkeg5pcjj3bi4crh4r86oywyhgagbwj4vcoudv...@mail.gmail.com,
on 08/28/2013
at 11:03 AM, John Gilmore jwgli...@gmail.com said:
As Chris Blaicher and Sam Siegel have suggested, PAUSE/RELEASE is
logically complete. Anything that can be accomplished with WAIT/POST
can be accomplished,
On 29/08/2013 12:13 AM, Paul Gilmartin wrote:
On Tue, 27 Aug 2013 19:48:25 -0400, Blaicher, Christopher Y. wrote:
There are lots of ways to do this. Some of the questions you have to first ask
are: 1) Are the tasks asynchronous to each other? 2) Can there be more than one
slave task? 3)
42 matches
Mail list logo
