Re: [EXTERNAL] Re: EXTERNAL: Re: FedEx to move entirely to the cloud [Internal]

[Grant Taylor]

On 7/11/22 1:32 PM, Karl S Huf wrote:
I would refer anyone genuinely interested in sibling pend to 
download and review Dr. H. Pat Artis's "Sibling Pend: Like a Wheel 
Within a Wheel" 1996 CMG paper (available to download at Dr. Pat's 
site http://www.perfassoc.com ).  While the technology underpinning 
storage has changed a lot the concept of sibling pend really hasn't. 
I suspect this paper isn't new, though, for many on this list.


Thank you for the pointer to the paper as it's new to me.  The concept 
is not new, but the paper will be an interesting read.


Sibling PEND: Like a Wheel within a Wheel
Dr. H. Pat Artis - Published in 1996

Published in the Proceedings of CMG '96 Abstract: After more than 2 
decades of refining performance measurement and tuning strategies for 
traditional DASD devices and the MVS I/O subsystem, performance analysts 
are now presented with the vagaries of measurement and tuning for RAID-5 
based subsystems. While a variety of conceptual models might be proposed 
to explain the performance characteristics of these subsystems, this 
paper will focus on the author's paradigm of a physical I/O subsystem 
within the logical MVS I/O subsystem and the sibling PEND which results 
from collisions within the physical disk subsystem.


http://www.perfassoc.com/register.php/pdf/papers/sibling_pend_paper_96.pdf



--
Grant. . . .
unix || die

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Warren Brown]

 Hey mainframers is Rob Jackson still doing updates?
On Monday, July 11, 2022 at 01:12:05 PM EDT, Charles Mills 
 wrote:  
 
 App received

HOW NOW,    BROWN COW

Quoting the command preserves the lower case, even with the embedded blanks. 
(No, I did not test every permutation.)

/F procname,'How now,    Brown Cow'

App received 'How now,    Brown Cow'

Note that the quotes are included in what the app receives.

JCL PARM= is a little more consistent. //S1 EXEC FOO,PARM=HOW NOW BROWN COW

Will pass only HOW to the app.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, July 11, 2022 9:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?



how about:
 /F procname,How now,    Brown Cow
(multiple spaces?)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
  

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: EXTERNAL: Re: FedEx to move entirely to the cloud [Internal]

[Karl S Huf]

I would refer anyone genuinely interested in sibling pend to download and 
review Dr. H. Pat Artis's "Sibling Pend: Like a Wheel Within a Wheel" 1996 CMG 
paper (available to download at Dr. Pat's site http://www.perfassoc.com ).  
While the technology underpinning storage has changed a lot the concept of 
sibling pend really hasn't.  I suspect this paper isn't new, though, for many 
on this list.


NTAC:3NS-20

-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Pommier, Rex
Sent: Monday, July 11, 2022 10:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [EXT] Re: [EXTERNAL] Re: EXTERNAL: Re: FedEx to move entirely to the 
cloud [Internal]

This email originated from outside the organization.  Do not click links or 
open attachments unless you have verified this email is legitimate.

Hi Phil,

That is odd that there isn't more written about sibling pend.  IDK if solid 
state disk suffers to the same extent as spinning spindles but I would guess 
not.  Short description is that typical disk array configuration was to take 
the disks and carve them up into a bunch of smaller LUNs then distribute these 
LUNs out to the various servers sharing the array storage.  Think of how many 
3390-mod9s can fit on a 600 GB drive - and that's a small drive these days.  So 
when you're sharing the array between mainframe and Unix (in our case) or 
Windows, you can end up with some of the physical disk blocks being assigned to 
3390s and some to the other platforms.  Sibling pend is simply when one of the 
servers (or in our case the array itself on behalf of one of the Unix boxes) 
hogs all the I/O capability of the disk spindle, and doesn't allow any of the 
other hosts that need data off the spindle to get to it.

In our case, the mainframe was waiting up to a half second to get a single I/O 
from the spindles that were being consumed by the Unix/Oracle process.

Rex

Rex Pommier wrote, in part:
> I finally got a physical drive mapping from them and discovered it was
sibling pend between .



This "sibling pend" is intriguing. A grand total of 18 hits on Google; most of 
them are about DASD, so it's clear you didn't typo it or mishear it. But only 
18 seems unlikely, especially since the refs go back to 1996! Very odd.
I'd've thought in 25+ years there would have to have been more written about it.



I can't get much from those 18 links (paywalls etc.), and would love to 
understand this better, just for curiosity's sake-it's of no practical use to 
me in my current role. Anyone got any more details?



...phsiii (who is pretty sure there was some "sibling pend" between him and his 
sisters while growing up)


--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

ISFSLASH, MGCRE? ...?

[Paul Gilmartin]

On Mon, 11 Jul 2022 10:11:51 -0700, Charles Mills wrote:
>...
>Quoting the command preserves the lower case, even with the embedded blanks. 
>(No, I did not test every permutation.)
>/F procname,'How now, Brown Cow'
>App received 'How now, Brown Cow'
>
I had been working on the hypothesis that ISFSLASH uses MGCRE MF=E to issue the 
command.
However, in the doc for that I find:
  Operator commands may contain the following characters:
A to Z
0 to 9
' # $ & ( ) * + , - . / ¢ < | ! ; ¬ % _ > ? : @ " =

No space; no lower case.  Should I look elsewhere or submit an RCF?

Is this an example of a mid-level interface over specifying characteristics
of a lower-level function?

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: DUMPs protection question

[Binyamin Dissen]

On Mon, 11 Jul 2022 15:40:10 + "jgmauta...@yahoo.com.ar"
<01f9499d67db-dmarc-requ...@listserv.ua.edu> wrote:

:>Hi!
:>
:>I have a question regarding IEAABD.DMPAUTH / IEAABD.DMPAKEY resources in RACF 
FACILITY class:
:>
:>
:>1-  In this context, when the RACF "Security Administrator Guide" says 
"controlled programs", is it referring to programs protected in RACF PROGRAM 
class?

Also EXECUTE access.

:>2-  It is not completely clear to me, from the documentation, what 
happens when these resources are UNPROTECTED (NO RACF profile protecting these 
resources).
:>In that case, are all users indeed allowed to obtain such a DUMP (using 
SYSUDUMP, SYSABEND, or SYSMDUMP DD in JCL)? I assume the answer is YES, but I 
want to be sure.

Yes.

:>3-  If you decide to implement this level of DUMP control by protecting 
these resources in RACF FACILITY class, what precautions should you take?
:>I am not worried about humans needing these authorizations (probably just 
sysprogs), but what about users assigned to STCs?

SVCDUMPs are not controlled by this. Not sure why STCs should be treated
differently.


--
Binyamin Dissen 
http://www.dissensoftware.com

Director, Dissen Software, Bar & Grill - Israel

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Paul Gilmartin]

On Mon, 11 Jul 2022 10:11:51 -0700, Charles Mills  wrote:
>...
>/F procname,'How now, Brown Cow'
>App received 'How now, Brown Cow'
>
>Note that the quotes are included in what the app receives.
>
But how did you enter the command?
o From an operator's console?
o From HLASM MGCRE?
o From an SDSF panel?
o From ISFSLASH?

The "/F" narrows the choice.  But there's still a cascade of interfaces.
The treatment of quotes resembles HLASM macro argument processing.
What does it do with:
o Internal apostrophes, single, doubled, and unbalanced?
o Internal amperrsandss, single, doubled?
It suffices to say, "not documented."  In which case it should be --
experiment should be only a validation.  "As enny fool kin plainly see!"
is not documentation.

>JCL PARM= is a little more consistent. //S1 EXEC FOO,PARM=HOW NOW BROWN COW
>Will pass only HOW to the app.
> 
BTDT.

-- 
Thanks,
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: NOTSP The Latin of Software Code Is Thriving - The New York Times

[Colin Paice]

My comments about
1. A million times a second... etc

Were from about 30 years ago, before optimization improved.

I know that the "hot" instruction for MQ on z/OS that showed up in
profiling,  was the Load/Update Address of the next free slot in the trace
buffer in ECSA.
When there were many concurrent threads using MQ trace, they all used this
field.  Sometimes the field was on the same chip.  Sometimes it was in a
different "book"  (and so the time to get this field was 1000 times the
duration if it was in the same CPU)
By giving each TCB its own trace buffer this hotspot disappeared!

The compiler could not optimize this. Only a change of design could fix it.

Colin

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Charles Mills]

App received

HOW NOW, BROWN COW

Quoting the command preserves the lower case, even with the embedded blanks. 
(No, I did not test every permutation.)

/F procname,'How now, Brown Cow'

App received 'How now, Brown Cow'

Note that the quotes are included in what the app receives.

JCL PARM= is a little more consistent. //S1 EXEC FOO,PARM=HOW NOW BROWN COW

Will pass only HOW to the app.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, July 11, 2022 9:44 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?



how about:
 /F procname,How now, Brown Cow
(multiple spaces?)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

ISFDELAY

[Paul Gilmartin]

ISFDELAY
specifies the response delay limit for system commands. Specify 
ISFDELAY="timeout-value",
where timeout-value specifies the default timeout value (in seconds) for 
which SDSF will wait
for message responses to the slash / command. The timeout value must be in 
the range of
0 to  seconds, where 0 indicates that SDSF will neither wait nor 
display message
responses on the message line.

The message responses are still written to the user session log. The 
default timeout value
is 1 second. SDSF waits until the timeout value has passed or the first 
response is received.

That's B.S.!  It should be "the last response",  not "the first response".  But 
I fear the SDSF
developers did the best they  could.

The feckless MVS designers should provide an indication to every API that the 
last response
has been posted.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Paul Gilmartin]

On Mon, 11 Jul 2022 09:12:45 -0700, Charles Mills wrote:

>The problem is that there just is no generic MODIFY format, and I guess there 
>really is no universal console command format. Yes, yes, the next time they 
>write MVS they should do a single parser shared among all commands, but 
>unfortunately they did not do it for this MVS. 
> 
It's only half as bad as you make it sound.  But there should have
been some lexical uniformity, such as: "Apostrophes always protect
speciall characters."

>For MODIFY, the command I am most familiar with, EVERYTHING after the procname 
>and so forth is passed to the application. I just verified this. For a test 
>app I have, I entered
>
>/F procname,how now brown cow
>
how about:
 /F procname,How now, Brown Cow
(multiple spaces?)

>And verified that what the application received in the CIB was
>
>HOW NOW BROWN COW
>
Who forces upper case?  What If I want:
/F procname,PATH: /dev/null

>What a given application might choose to do with that is entirely up to that 
>application, of course. No MVS-generic documentation is possible. (Other than 
>"your results may vary.")
> 
That's proper provided that the application's documentation
specified the behavior, even as the JCL Ref. doesn't specify
every program's interpretation of PARM.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: NOTSP The Latin of Software Code Is Thriving - The New York Times

[Charles Mills]

+1

And when new hardware comes out, taking advantage of the new architecture is a 
simple matter of updating ARCH() in your C/C++ compile and re-building. You 
probably don't have the appetite to re-work your carefully hand-tuned assembler.

I know whereof I speak. I wrote a commercial product in C++ that successfully 
handled millions of events per second, with CPU utilization that was considered 
satisfactory by customers. Non-trivial events: basically taking an SMF record, 
reformatting a hundred or more fields using a "report writer"* type 
architecture, translating it to UTF-8 (non-trivial) and pushing it out the TCP 
stack.

*By report writer type architecture, I mean it did not work the way you would 
write a hard-coded program, working its way through one SMF record section at a 
time. It went customer-specified-field by customer-specified-field, so for two 
adjacent fields in the same section, it had to decode the relevant triplet 
twice.

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Andrew Rowley
Sent: Sunday, July 10, 2022 6:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: NOTSP The Latin of Software Code Is Thriving - The New York Times

On 9/07/2022 1:10 am, Colin Paice wrote:
> I was told
> If it executes
>
> 1. a million times a second - write in assembler
> 2. a thousand times a second write it in cobol or C
> 3. once a second - write it in Java
> 4. Else /bash/rexx/
Probably not an accurate picture these days.

It would have to be a very select piece of assembler to have any 
significant advantage over C / C++. C and C++ have the advantage that 
the compiler doesn't have to produce maintainable or comprehensible 
code, so it can do lots of optimizations, inlining, loop unrolling etc. 
- whatever the compiler writers found produces the fastest code. Of 
course you can do the same in assembler - it is just a question of 
whether it is practicable for larger pieces of code.

Java: that is probably reasonable if you are talking about starting a 
JVM from scratch every time e.g. like a z/OS batch job. If you are 
talking about a routine executed by a running program, I would expect 
Java to be close to C. (Certainly not 3 orders of magnitude different.)

-- 
Andrew Rowley
Black Hill Software

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Charles Mills]

The problem is that there just is no generic MODIFY format, and I guess there 
really is no universal console command format. Yes, yes, the next time they 
write MVS they should do a single parser shared among all commands, but 
unfortunately they did not do it for this MVS. 

For MODIFY, the command I am most familiar with, EVERYTHING after the procname 
and so forth is passed to the application. I just verified this. For a test app 
I have, I entered

/F procname,how now brown cow

And verified that what the application received in the CIB was

HOW NOW BROWN COW

What a given application might choose to do with that is entirely up to that 
application, of course. No MVS-generic documentation is possible. (Other than 
"your results may vary.")

Charles


-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Paul Gilmartin
Sent: Monday, July 11, 2022 8:00 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?

On Mon, 11 Jul 2022 13:42:07 +, Peter Relson wrote:

>Shmuel write
>> A space in an operator command is the separator between operand and comment.
>
>"Can be", not "is". It depends on the command.
> 
Is this clearly documented for each command?

Does the doc cover the case of passing a string containing a blank as a
command operand?  "Don't do that!" is not a satisfactory answer.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Paul Gilmartin]

On Mon, 11 Jul 2022 11:52:40 +, Seymour J Metz wrote:

>ObNit Why don't you want to quoute the stem name? The statement address SDSF  
>"ISFSLASH (mycmd.) (WAIT)" will work regardless of whether you give mycomd. a 
>default value.
> 
The flaw occurs in the User's Guide.  RCF submitted.

Another in progress about an error in the syntax diagram.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

DUMPs protection question

[jgmauta...@yahoo.com.ar]

Hi!

I have a question regarding IEAABD.DMPAUTH / IEAABD.DMPAKEY resources in RACF 
FACILITY class:


1-  In this context, when the RACF "Security Administrator Guide" says 
"controlled programs", is it referring to programs protected in RACF PROGRAM 
class?



2-  It is not completely clear to me, from the documentation, what happens 
when these resources are UNPROTECTED (NO RACF profile protecting these 
resources).
In that case, are all users indeed allowed to obtain such a DUMP (using 
SYSUDUMP, SYSABEND, or SYSMDUMP DD in JCL)? I assume the answer is YES, but I 
want to be sure.



3-  If you decide to implement this level of DUMP control by protecting 
these resources in RACF FACILITY class, what precautions should you take?
I am not worried about humans needing these authorizations (probably just 
sysprogs), but what about users assigned to STCs?
Thanks in advance for your help,
Juan G. Mautalen

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: [EXTERNAL] Re: EXTERNAL: Re: FedEx to move entirely to the cloud [Internal]

[Pommier, Rex]

Hi Phil,

That is odd that there isn't more written about sibling pend.  IDK if solid 
state disk suffers to the same extent as spinning spindles but I would guess 
not.  Short description is that typical disk array configuration was to take 
the disks and carve them up into a bunch of smaller LUNs then distribute these 
LUNs out to the various servers sharing the array storage.  Think of how many 
3390-mod9s can fit on a 600 GB drive - and that's a small drive these days.  So 
when you're sharing the array between mainframe and Unix (in our case) or 
Windows, you can end up with some of the physical disk blocks being assigned to 
3390s and some to the other platforms.  Sibling pend is simply when one of the 
servers (or in our case the array itself on behalf of one of the Unix boxes) 
hogs all the I/O capability of the disk spindle, and doesn't allow any of the 
other hosts that need data off the spindle to get to it.  

In our case, the mainframe was waiting up to a half second to get a single I/O 
from the spindles that were being consumed by the Unix/Oracle process.  

Rex

Rex Pommier wrote, in part:
> I finally got a physical drive mapping from them and discovered it was
sibling pend between .

 

This "sibling pend" is intriguing. A grand total of 18 hits on Google; most of 
them are about DASD, so it's clear you didn't typo it or mishear it. But only 
18 seems unlikely, especially since the refs go back to 1996! Very odd.
I'd've thought in 25+ years there would have to have been more written about it.

 

I can't get much from those 18 links (paywalls etc.), and would love to 
understand this better, just for curiosity's sake-it's of no practical use to 
me in my current role. Anyone got any more details?

 

...phsiii (who is pretty sure there was some "sibling pend" between him and his 
sisters while growing up)


--
The information contained in this message is confidential, protected from 
disclosure and may be legally privileged. If the reader of this message is not 
the intended recipient or an employee or agent responsible for delivering this 
message to the intended recipient, you are hereby notified that any disclosure, 
distribution, copying, or any action taken or action omitted in reliance on it, 
is strictly prohibited and may be unlawful. If you have received this 
communication in error, please notify us immediately by replying to this 
message and destroy the material in its entirety, whether in electronic or hard 
copy format. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Paul Gilmartin]

On Mon, 11 Jul 2022 13:42:07 +, Peter Relson wrote:

>Shmuel write
>> A space in an operator command is the separator between operand and comment.
>
>"Can be", not "is". It depends on the command.
> 
Is this clearly documented for each command?

Does the doc cover the case of passing a string containing a blank as a
command operand?  "Don't do that!" is not a satisfactory answer.

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Weird TAPE MOUNT behavior

[Jack Zukt]

That is what I am betting on. Something is being done by DB2 or SORT that
keeps the "TAPE ON" message from showing for such a long time. I was hoping
for someone that had experienced this situation before.
Jack

On Mon, 11 Jul 2022 at 15:00, Jack Zukt  wrote:

> Yes, they are all VTS drives
> And there are no IEF455D pending messages for the duration of the. And
> multiple jobs usinf PRIVAT tapes were executed while this one had this
> behavior. Which occurred on all the various runs from the first one, until
> and including the last ones (which was successful, as it was not canceled)
> Jack
>
>
> On Mon, 11 Jul 2022 at 14:46, Clifford McNeill  wrote:
>
>> The IEF455D msg is probably in the syslog not the joblog.  I think it
>> might be the key.  I see tape mounts on device 7070 and later on 3671.
>> Are they both VTS drives?
>>
>> On 7/11/2022 8:34 AM, Jack Zukt wrote:
>> > Not likely
>> > This is the relevant JOB LOG
>> >
>> > J E S 2  J O B  L O G  --  S Y S T E M  S Y A
>> 1  --
>> >   N O D E  P R D 1
>> >
>> >
>> > 05.34.24 J1234567  SUNDAY,10 JUL 2022 
>> >
>> > 05.34.24 J1234567  IRR010I  USERID OPCDB2P  IS ASSIGNED TO THIS JOB.
>> >
>> > 05.34.24 J1234567  ICH70001I OPCDB2P  LAST ACCESS AT 05:34:24 ON SUNDAY,
>> > JULY 10, 2022
>> > 05.34.24 J1234567  $HASP373 DB2PRJ1O STARTED - INIT 123  - CLASS X
>>   -
>> > SYS SYA1
>> > 05.34.24 J1234567  IEF403I DB2PRJ1O - STARTED - TIME=05.34.24
>> >
>> > 05.34.30 J1234567  IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  934
>> >
>> > 934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,
>> >
>> > 934 OR RESPOND TO IEF455D MESSAGE
>> >
>> > 09.44.53 J1234567  IEC705I TAPE ON
>> >
>> 7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> >
>> > 10.32.11 J1234567  IEC502E K
>> > 7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 10.32.11 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 10.32.13 J1234567  IEC705I TAPE ON
>> >
>> 7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> >
>> > 11.18.55 J1234567  IEC502E K
>> > 7070,CTX929,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 11.18.55 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 11.18.56 J1234567  IEC705I TAPE ON
>> >
>> 7070,ZJM806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> >
>> > 12.03.07 J1234567  IEC502E K
>> > 7070,ZJM806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 12.03.07 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 12.03.08 J1234567  IEC705I TAPE ON
>> >
>> 7070,ZJU586,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> >
>> > 12.42.19 J1234567  IEC502E K
>> > 7070,ZJU586,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 12.42.19 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 12.42.21 J1234567  IEC705I TAPE ON
>> >
>> 7070,ZNA893,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> > 13.23.20 J1234567  IEC502E K
>> > 7070,ZNA893,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 13.23.20 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 13.23.21 J1234567  IEC705I TAPE ON
>> >
>> 7070,ZJ8806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> > 14.01.45 J1234567  IEC502E K
>> > 7070,ZJ8806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 14.01.45 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 14.01.47 J1234567  IEC705I TAPE ON
>> >
>> 7070,ZNM441,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> > 14.43.06 J1234567  IEC502E K
>> > 7070,ZNM441,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 14.43.06 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 14.43.08 J1234567  IEC705I TAPE ON
>> >
>> 7070,ZKF268,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> > 15.25.01 J1234567  IEC502E K
>> > 7070,ZKF268,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 15.25.01 J1234567  IEC501A M
>> >
>> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
>> >
>> > 15.25.02 J1234567  IEC705I TAPE ON
>> >
>> 7070,ZKK820,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
>> > 16.43.45 J1234567  IEC205I SYS6,DB2PRJ1O,PRDB2PRC,FILESEQ=1,
>> COMPLETE
>> > VOLUME LIST,  910
>> > 910 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,
>> >
>> > 910
>> > 

Re: Weird TAPE MOUNT behavior

[Jack Zukt]

Yes, they are all VTS drives
And there are no IEF455D pending messages for the duration of the. And
multiple jobs usinf PRIVAT tapes were executed while this one had this
behavior. Which occurred on all the various runs from the first one, until
and including the last ones (which was successful, as it was not canceled)
Jack


On Mon, 11 Jul 2022 at 14:46, Clifford McNeill  wrote:

> The IEF455D msg is probably in the syslog not the joblog.  I think it
> might be the key.  I see tape mounts on device 7070 and later on 3671.
> Are they both VTS drives?
>
> On 7/11/2022 8:34 AM, Jack Zukt wrote:
> > Not likely
> > This is the relevant JOB LOG
> >
> > J E S 2  J O B  L O G  --  S Y S T E M  S Y A 1
> --
> >   N O D E  P R D 1
> >
> >
> > 05.34.24 J1234567  SUNDAY,10 JUL 2022 
> >
> > 05.34.24 J1234567  IRR010I  USERID OPCDB2P  IS ASSIGNED TO THIS JOB.
> >
> > 05.34.24 J1234567  ICH70001I OPCDB2P  LAST ACCESS AT 05:34:24 ON SUNDAY,
> > JULY 10, 2022
> > 05.34.24 J1234567  $HASP373 DB2PRJ1O STARTED - INIT 123  - CLASS X
>   -
> > SYS SYA1
> > 05.34.24 J1234567  IEF403I DB2PRJ1O - STARTED - TIME=05.34.24
> >
> > 05.34.30 J1234567  IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  934
> >
> > 934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,
> >
> > 934 OR RESPOND TO IEF455D MESSAGE
> >
> > 09.44.53 J1234567  IEC705I TAPE ON
> >
> 7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> >
> > 10.32.11 J1234567  IEC502E K
> > 7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 10.32.11 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 10.32.13 J1234567  IEC705I TAPE ON
> >
> 7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> >
> > 11.18.55 J1234567  IEC502E K
> > 7070,CTX929,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 11.18.55 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 11.18.56 J1234567  IEC705I TAPE ON
> >
> 7070,ZJM806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> >
> > 12.03.07 J1234567  IEC502E K
> > 7070,ZJM806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 12.03.07 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 12.03.08 J1234567  IEC705I TAPE ON
> >
> 7070,ZJU586,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> >
> > 12.42.19 J1234567  IEC502E K
> > 7070,ZJU586,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 12.42.19 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 12.42.21 J1234567  IEC705I TAPE ON
> >
> 7070,ZNA893,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> > 13.23.20 J1234567  IEC502E K
> > 7070,ZNA893,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 13.23.20 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 13.23.21 J1234567  IEC705I TAPE ON
> >
> 7070,ZJ8806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> > 14.01.45 J1234567  IEC502E K
> > 7070,ZJ8806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 14.01.45 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 14.01.47 J1234567  IEC705I TAPE ON
> >
> 7070,ZNM441,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> > 14.43.06 J1234567  IEC502E K
> > 7070,ZNM441,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 14.43.06 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 14.43.08 J1234567  IEC705I TAPE ON
> >
> 7070,ZKF268,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> > 15.25.01 J1234567  IEC502E K
> > 7070,ZKF268,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 15.25.01 J1234567  IEC501A M
> >
> 7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01
> >
> > 15.25.02 J1234567  IEC705I TAPE ON
> >
> 7070,ZKK820,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
> > 16.43.45 J1234567  IEC205I SYS6,DB2PRJ1O,PRDB2PRC,FILESEQ=1, COMPLETE
> > VOLUME LIST,  910
> > 910 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,
> >
> > 910
> > VOLS=CTX817,CTX929,ZJM806,ZJU586,ZNA893,ZJ8806,ZNM441,ZKF268,
> >
> > 910 VOLS=ZKK820,TOTALBLOCKS=17103027
> >
> > 16.43.52 J1234567  IEF234E K 7070,ZKK820,PVT,DB2PRJ1O,PRDB2PRC
> >
> > 16.46.11 J1234567  IEF233D M 3671,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  026
> >
> > 026 DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,
> >
> > 026 OR RESPOND TO IEF455D MESSAGE
> >
> > 

Re: Weird TAPE MOUNT behavior

[Carmen Vitullo]

I wonder if this is a deferred mount? without knowing what DB2 job is 
running it maybe doing some processing on DASD, then writing to tape?


Carmen

On 7/11/2022 8:46 AM, Clifford McNeill wrote:
The IEF455D msg is probably in the syslog not the joblog.  I think it 
might be the key.  I see tape mounts on device 7070 and later on 
3671.   Are they both VTS drives?


On 7/11/2022 8:34 AM, Jack Zukt wrote:

Not likely
This is the relevant JOB LOG

    J E S 2  J O B  L O G  --  S Y S T E M S Y A 
1  --

  N O D E  P R D 1


05.34.24 J1234567  SUNDAY,    10 JUL 2022 

05.34.24 J1234567  IRR010I  USERID OPCDB2P  IS ASSIGNED TO THIS JOB.

05.34.24 J1234567  ICH70001I OPCDB2P  LAST ACCESS AT 05:34:24 ON SUNDAY,
JULY 10, 2022
05.34.24 J1234567  $HASP373 DB2PRJ1O STARTED - INIT 123  - CLASS 
X    -

SYS SYA1
05.34.24 J1234567  IEF403I DB2PRJ1O - STARTED - TIME=05.34.24

05.34.30 J1234567  IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC, 934

    934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

    934 OR RESPOND TO IEF455D MESSAGE

09.44.53 J1234567  IEC705I TAPE ON
7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 



10.32.11 J1234567  IEC502E K
7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

10.32.11 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



10.32.13 J1234567  IEC705I TAPE ON
7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 



11.18.55 J1234567  IEC502E K
7070,CTX929,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

11.18.55 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



11.18.56 J1234567  IEC705I TAPE ON
7070,ZJM806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 



12.03.07 J1234567  IEC502E K
7070,ZJM806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.03.07 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



12.03.08 J1234567  IEC705I TAPE ON
7070,ZJU586,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 



12.42.19 J1234567  IEC502E K
7070,ZJU586,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.42.19 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



12.42.21 J1234567  IEC705I TAPE ON
7070,ZNA893,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 


13.23.20 J1234567  IEC502E K
7070,ZNA893,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

13.23.20 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



13.23.21 J1234567  IEC705I TAPE ON
7070,ZJ8806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 


14.01.45 J1234567  IEC502E K
7070,ZJ8806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.01.45 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



14.01.47 J1234567  IEC705I TAPE ON
7070,ZNM441,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 


14.43.06 J1234567  IEC502E K
7070,ZNM441,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.43.06 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



14.43.08 J1234567  IEC705I TAPE ON
7070,ZKF268,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 


15.25.01 J1234567  IEC502E K
7070,ZKF268,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

15.25.01 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01 



15.25.02 J1234567  IEC705I TAPE ON
7070,ZKK820,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2 

16.43.45 J1234567  IEC205I SYS6,DB2PRJ1O,PRDB2PRC,FILESEQ=1, 
COMPLETE

VOLUME LIST,  910
    910 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

    910
VOLS=CTX817,CTX929,ZJM806,ZJU586,ZNA893,ZJ8806,ZNM441,ZKF268,

    910 VOLS=ZKK820,TOTALBLOCKS=17103027

16.43.52 J1234567  IEF234E K 7070,ZKK820,PVT,DB2PRJ1O,PRDB2PRC

16.46.11 J1234567  IEF233D M 3671,PRIVAT,SL,DB2PRJ1O,PRDB2PRC, 026

    026 DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,

    026 OR RESPOND TO IEF455D MESSAGE

16.52.28 J1234567  IEC705I TAPE ON
3671,ZKS152,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,MEDIA2 



17.48.41 J1234567  IEC205I SYS00010,DB2PRJ1O,PRDB2PRC,FILESEQ=1, 
COMPLETE

VOLUME LIST,  298
    298 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,VOLS=ZKS152,

    298 TOTALBLOCKS=1069901

17.48.43 J1234567  IEF234E K 3671,ZKS152,PVT,DB2PRJ1O,PRDB2PRC

19.12.37 J1234567  - --TIMINGS
(MINS.)--    PAGING COUNTS---
19.12.37 J1234567  -JOBNAME  STEPNAME PROCSTEP    RC   EXCP CPU    SRB
  CLOCK   SERV  PG   PAGE   SWAP    VIO SWAPS STEPNO
19.12.37 J1234567  -DB2PRJ1O  

Re: Weird TAPE MOUNT behavior

[Clifford McNeill]

The IEF455D msg is probably in the syslog not the joblog.  I think it 
might be the key.  I see tape mounts on device 7070 and later on 3671.   
Are they both VTS drives?


On 7/11/2022 8:34 AM, Jack Zukt wrote:

Not likely
This is the relevant JOB LOG

J E S 2  J O B  L O G  --  S Y S T E M  S Y A 1  --
  N O D E  P R D 1


05.34.24 J1234567  SUNDAY,10 JUL 2022 

05.34.24 J1234567  IRR010I  USERID OPCDB2P  IS ASSIGNED TO THIS JOB.

05.34.24 J1234567  ICH70001I OPCDB2P  LAST ACCESS AT 05:34:24 ON SUNDAY,
JULY 10, 2022
05.34.24 J1234567  $HASP373 DB2PRJ1O STARTED - INIT 123  - CLASS X-
SYS SYA1
05.34.24 J1234567  IEF403I DB2PRJ1O - STARTED - TIME=05.34.24

05.34.30 J1234567  IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  934

934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

934 OR RESPOND TO IEF455D MESSAGE

09.44.53 J1234567  IEC705I TAPE ON
7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

10.32.11 J1234567  IEC502E K
7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

10.32.11 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

10.32.13 J1234567  IEC705I TAPE ON
7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

11.18.55 J1234567  IEC502E K
7070,CTX929,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

11.18.55 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

11.18.56 J1234567  IEC705I TAPE ON
7070,ZJM806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

12.03.07 J1234567  IEC502E K
7070,ZJM806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.03.07 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.03.08 J1234567  IEC705I TAPE ON
7070,ZJU586,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

12.42.19 J1234567  IEC502E K
7070,ZJU586,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.42.19 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.42.21 J1234567  IEC705I TAPE ON
7070,ZNA893,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
13.23.20 J1234567  IEC502E K
7070,ZNA893,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

13.23.20 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

13.23.21 J1234567  IEC705I TAPE ON
7070,ZJ8806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
14.01.45 J1234567  IEC502E K
7070,ZJ8806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.01.45 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.01.47 J1234567  IEC705I TAPE ON
7070,ZNM441,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
14.43.06 J1234567  IEC502E K
7070,ZNM441,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.43.06 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.43.08 J1234567  IEC705I TAPE ON
7070,ZKF268,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
15.25.01 J1234567  IEC502E K
7070,ZKF268,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

15.25.01 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

15.25.02 J1234567  IEC705I TAPE ON
7070,ZKK820,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
16.43.45 J1234567  IEC205I SYS6,DB2PRJ1O,PRDB2PRC,FILESEQ=1, COMPLETE
VOLUME LIST,  910
910 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

910
VOLS=CTX817,CTX929,ZJM806,ZJU586,ZNA893,ZJ8806,ZNM441,ZKF268,

910 VOLS=ZKK820,TOTALBLOCKS=17103027

16.43.52 J1234567  IEF234E K 7070,ZKK820,PVT,DB2PRJ1O,PRDB2PRC

16.46.11 J1234567  IEF233D M 3671,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  026

026 DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,

026 OR RESPOND TO IEF455D MESSAGE

16.52.28 J1234567  IEC705I TAPE ON
3671,ZKS152,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,MEDIA2

17.48.41 J1234567  IEC205I SYS00010,DB2PRJ1O,PRDB2PRC,FILESEQ=1, COMPLETE
VOLUME LIST,  298
298 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,VOLS=ZKS152,

298 TOTALBLOCKS=1069901

17.48.43 J1234567  IEF234E K 3671,ZKS152,PVT,DB2PRJ1O,PRDB2PRC

19.12.37 J1234567  - --TIMINGS
(MINS.)--PAGING COUNTS---
19.12.37 J1234567  -JOBNAME  STEPNAME PROCSTEPRC   EXCPCPUSRB
  CLOCK   SERV  PG   PAGE   SWAPVIO SWAPS STEPNO
19.12.37 J1234567  -DB2PRJ1O  PRDB2PRC04 18349K 108.19
2.91 818.20 858556   0472  0  0 0 1

On Mon, 11 Jul 2022 at 14:32, Clifford McNeill  wrote:


Did you run 

Re: How do I issue a command with a blank in it?

[Peter Relson]

Shmuel write
> A space in an operator command is the separator between operand and comment.

"Can be", not "is". It depends on the command.

Peter Relson
z/OS Core Technology Design


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Weird TAPE MOUNT behavior

[Carmen Vitullo]

I see the joblog, was there any other messages on the syslog around that 
time, for DB2 archive offload I usually see MOUNT TAPE on  or REPLY.


Carmen

On 7/11/2022 8:23 AM, Jack Zukt wrote:

Hi all,

Last night we had a weird situation that prompted the operations people to
contact one of our standby teams.

A DB2 job started running and requested a PRIVAT tape:

05.34.24 J1234567  IEF403I DB2PRJ1O - STARTED - TIME=05.34.24

05.34.30 J1234567  IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  934

934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

934 OR RESPOND TO IEF455D MESSAGE

The "TAPE ON" message for this PRIVAT tape was not issued until more than
four hours later:
09.44.53 J1234567  IEC705I TAPE ON
7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2


and another forty minutes went by until that tape was unmounted and a new
one was requested:

10.32.11 J1234567  IEC502E K
7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

10.32.11 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

However, this time, the "TAPE ON" message was immediate, as expected under
normal conditions:
10.32.13 J1234567  IEC705I TAPE ON
7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2


This run was the one that was executed without glitches as the first time
around the operations people contacted a standby team, the job was
cancelled and then resubmitted again (a few times).

I am not sure about what DB2 was doing but SORT was being used.

So, my question here is, why the first "TAPE ON" message was not issued
right after the MOUNT message?
Any help will be greatly appreciated
Thank you
jack

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN



--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Weird TAPE MOUNT behavior

[Jack Zukt]

Not likely
This is the relevant JOB LOG

   J E S 2  J O B  L O G  --  S Y S T E M  S Y A 1  --
 N O D E  P R D 1


05.34.24 J1234567  SUNDAY,10 JUL 2022 

05.34.24 J1234567  IRR010I  USERID OPCDB2P  IS ASSIGNED TO THIS JOB.

05.34.24 J1234567  ICH70001I OPCDB2P  LAST ACCESS AT 05:34:24 ON SUNDAY,
JULY 10, 2022
05.34.24 J1234567  $HASP373 DB2PRJ1O STARTED - INIT 123  - CLASS X-
SYS SYA1
05.34.24 J1234567  IEF403I DB2PRJ1O - STARTED - TIME=05.34.24

05.34.30 J1234567  IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  934

   934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

   934 OR RESPOND TO IEF455D MESSAGE

09.44.53 J1234567  IEC705I TAPE ON
7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

10.32.11 J1234567  IEC502E K
7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

10.32.11 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

10.32.13 J1234567  IEC705I TAPE ON
7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

11.18.55 J1234567  IEC502E K
7070,CTX929,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

11.18.55 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

11.18.56 J1234567  IEC705I TAPE ON
7070,ZJM806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

12.03.07 J1234567  IEC502E K
7070,ZJM806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.03.07 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.03.08 J1234567  IEC705I TAPE ON
7070,ZJU586,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2

12.42.19 J1234567  IEC502E K
7070,ZJU586,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.42.19 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

12.42.21 J1234567  IEC705I TAPE ON
7070,ZNA893,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
13.23.20 J1234567  IEC502E K
7070,ZNA893,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

13.23.20 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

13.23.21 J1234567  IEC705I TAPE ON
7070,ZJ8806,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
14.01.45 J1234567  IEC502E K
7070,ZJ8806,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.01.45 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.01.47 J1234567  IEC705I TAPE ON
7070,ZNM441,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
14.43.06 J1234567  IEC502E K
7070,ZNM441,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.43.06 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

14.43.08 J1234567  IEC705I TAPE ON
7070,ZKF268,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
15.25.01 J1234567  IEC502E K
7070,ZKF268,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

15.25.01 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

15.25.02 J1234567  IEC705I TAPE ON
7070,ZKK820,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2
16.43.45 J1234567  IEC205I SYS6,DB2PRJ1O,PRDB2PRC,FILESEQ=1, COMPLETE
VOLUME LIST,  910
   910 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

   910
VOLS=CTX817,CTX929,ZJM806,ZJU586,ZNA893,ZJ8806,ZNM441,ZKF268,

   910 VOLS=ZKK820,TOTALBLOCKS=17103027

16.43.52 J1234567  IEF234E K 7070,ZKK820,PVT,DB2PRJ1O,PRDB2PRC

16.46.11 J1234567  IEF233D M 3671,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  026

   026 DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,

   026 OR RESPOND TO IEF455D MESSAGE

16.52.28 J1234567  IEC705I TAPE ON
3671,ZKS152,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,MEDIA2

17.48.41 J1234567  IEC205I SYS00010,DB2PRJ1O,PRDB2PRC,FILESEQ=1, COMPLETE
VOLUME LIST,  298
   298 DSN=DB2PRDB.DSN1.DCSJO.#2022191.#1546.C01,VOLS=ZKS152,

   298 TOTALBLOCKS=1069901

17.48.43 J1234567  IEF234E K 3671,ZKS152,PVT,DB2PRJ1O,PRDB2PRC

19.12.37 J1234567  - --TIMINGS
(MINS.)--PAGING COUNTS---
19.12.37 J1234567  -JOBNAME  STEPNAME PROCSTEPRC   EXCPCPUSRB
 CLOCK   SERV  PG   PAGE   SWAPVIO SWAPS STEPNO
19.12.37 J1234567  -DB2PRJ1O  PRDB2PRC04 18349K 108.19
2.91 818.20 858556   0472  0  0 0 1

On Mon, 11 Jul 2022 at 14:32, Clifford McNeill  wrote:

> Did you run out of tape drives?  Can you show the IEF455D msg?
>
> On 7/11/2022 8:23 AM, Jack Zukt wrote:
> > RESPOND TO IEF455D MESSAGE
>
> --
> For IBM-MAIN subscribe / 

Re: Weird TAPE MOUNT behavior

[Clifford McNeill]

Did you run out of tape drives?  Can you show the IEF455D msg?

On 7/11/2022 8:23 AM, Jack Zukt wrote:

RESPOND TO IEF455D MESSAGE


--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Weird TAPE MOUNT behavior

[Jack Zukt]

Hi all,

Last night we had a weird situation that prompted the operations people to
contact one of our standby teams.

A DB2 job started running and requested a PRIVAT tape:

05.34.24 J1234567  IEF403I DB2PRJ1O - STARTED - TIME=05.34.24

05.34.30 J1234567  IEF233D M 7070,PRIVAT,SL,DB2PRJ1O,PRDB2PRC,  934

   934 DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,

   934 OR RESPOND TO IEF455D MESSAGE

The "TAPE ON" message for this PRIVAT tape was not issued until more than
four hours later:
09.44.53 J1234567  IEC705I TAPE ON
7070,CTX817,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2


and another forty minutes went by until that tape was unmounted and a new
one was requested:

10.32.11 J1234567  IEC502E K
7070,CTX817,SL,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

10.32.11 J1234567  IEC501A M
7070,PRIVAT,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01

However, this time, the "TAPE ON" message was immediate, as expected under
normal conditions:
10.32.13 J1234567  IEC705I TAPE ON
7070,CTX929,SL,COMP,DB2PRJ1O,PRDB2PRC,DB2PRDB.DSN1.DCSJO.#2022191.#0434.C01,MEDIA2


This run was the one that was executed without glitches as the first time
around the operations people contacted a standby team, the job was
cancelled and then resubmitted again (a few times).

I am not sure about what DB2 was doing but SORT was being used.

So, my question here is, why the first "TAPE ON" message was not issued
right after the MOUNT message?
Any help will be greatly appreciated
Thank you
jack

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Paul Gilmartin]

On Mon, 11 Jul 2022 12:29:15 +, Rob Scott wrote:

>True - however I think the original author of the exec was alternating between 
>using the stem form and a variable replacement form.
> 
How does it behave with SIGNAL ON NOVALUE in effect?
How does it behave with MYCMD.='Preseet' in effect?

>For my sins, this was cut+paste from a REXX PDS that we have for unit testing.
>
Has it been tested under both those condidions?

I suppose it's OK as long as you don't expose it in end user documentation.
(Or post it to a public forum.)


>From: Seymour J Metz
>Sent: 11 July 2022 12:53
>
>ObNit Why don't you want to quoute the stem name? The statement address SDSF 
>"ISFSLASH (mycmd.) (WAIT)" will work regardless of whether you give mycomd. a 
>default value.
>
If not quoted, it depends on the value assigned to the stem.


>
>From:  Rob Scott
>Sent: Monday, July 11, 2022 3:38 AM
>
>For what it is worth, SDSF REXX API already accepts an alternate form of input 
>for the ISFSLASH verb where you can pass the name of a stem variable that 
>holds one or more z/OS operator commands.
>
>For example :
>
>/* REXX */
>x=ISFCALLS("ON")
>ISFDELAY = 3
>mycmd.0 = 2
>mycmd.1 = "D A,L"
>mycmd.2 = "D T"
>address SDSF "ISFSLASH ("mycmd.") (WAIT)"
>do respindex = 1 to ISFULOG.0
>say ISFULOG.respindex
>end
>exit

-- 
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: How do I issue a command with a blank in it?

[Rob Scott]

True - however I think the original author of the exec was alternating between 
using the stem form and a variable replacement form.

For my sins, this was cut+paste from a REXX PDS that we have for unit testing.

Rob

From: IBM Mainframe Discussion List  On Behalf Of 
Seymour J Metz
Sent: 11 July 2022 12:53
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?

EXTERNAL EMAIL



ObNit Why don't you want to quoute the stem name? The statement address SDSF 
"ISFSLASH (mycmd.) (WAIT)" will work regardless of whether you give mycomd. a 
default value.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Rob 
Scott [rsc...@rocketsoftware.com]
Sent: Monday, July 11, 2022 3:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?

For what it is worth, SDSF REXX API already accepts an alternate form of input 
for the ISFSLASH verb where you can pass the name of a stem variable that holds 
one or more z/OS operator commands.

For example :

/* REXX */
x=ISFCALLS("ON")
ISFDELAY = 3
mycmd.0 = 2
mycmd.1 = "D A,L"
mycmd.2 = "D T"
address SDSF "ISFSLASH ("mycmd.") (WAIT)"
do respindex = 1 to ISFULOG.0
say ISFULOG.respindex
end
exit

Rob Scott
Rocket Software



-Original Message-
From: IBM Mainframe Discussion List 
mailto:IBM-MAIN@LISTSERV.UA.EDU>> On Behalf Of Paul 
Gilmartin
Sent: 10 July 2022 18:19
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?

EXTERNAL EMAIL





On Sun, 10 Jul 2022 11:51:29 -0400, David Spiegel wrote:

>Hi Gil,
>You said: "..as XEDIT and "sed" do ..."
>IIRC, TSO Edit should be included in this list.
>
Not in my list.



On Sun, 10 Jul 2022 16:06:18 +, Seymour J Metz wrote:

>A space in an operator command is the separator between operand and comment. 
>That means that space has to be treated differently from other characters. 
>What the RFE would ask for is to suspend that special treatment for spaces 
>within framiong characters.
>
Within an apostrophe-framed string the special treatment of numerous characters 
such as comma, parentheses, and the apostrophe itself is suspended, perhaps 
using TRT. It should be simple to add  to the list.

>I don't know how difficult it would be to change MGCR to allow, e.g., /text/, 
>as an alternative to 'text'.
>
I was focusing more on the SDSF API than on MGCR. But both may need changes, 
for similar
reasons: SDSF to allow an arbitrary string as an operator command; MGCR tp 
allow an arbitrary string as a parameter value.

--
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: 
INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupportdata=05%7C01%7Csmetz3%40gmu.edu%7Cb9093384306b44b6369b08da63106e95%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637931219486552276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=aNovhepzOOFX9oFnENhA8ANbaN6vrx6XxGNI8YYSrkA%3Dreserved=0
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferencesdata=05%7C01%7Csmetz3%40gmu.edu%7Cb9093384306b44b6369b08da63106e95%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637931219486552276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=c7eC9P36It97xMVm2b5pLCJAZWC%2FA4plj4Ssof%2BwQP0%3Dreserved=0
Privacy Policy - 

Re: How do I issue a command with a blank in it?

[Seymour J Metz]

ObNit Why don't you want to quoute the stem name? The statement address SDSF  
"ISFSLASH (mycmd.) (WAIT)" will work regardless of whether you give mycomd. a 
default value.


--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3


From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Rob 
Scott [rsc...@rocketsoftware.com]
Sent: Monday, July 11, 2022 3:38 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?

For what it is worth, SDSF REXX API already accepts an alternate form of input 
for the ISFSLASH verb where you can pass the name of a stem variable that holds 
one or more z/OS operator commands.

For example :

/* REXX */
x=ISFCALLS("ON")
ISFDELAY = 3
mycmd.0  = 2
mycmd.1  = "D A,L"
mycmd.2  = "D T"
address SDSF  "ISFSLASH ("mycmd.") (WAIT)"
do respindex = 1 to ISFULOG.0
  say ISFULOG.respindex
end
exit

Rob Scott
Rocket Software



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: 10 July 2022 18:19
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?

EXTERNAL EMAIL





On Sun, 10 Jul 2022 11:51:29 -0400, David Spiegel wrote:

>Hi Gil,
>You said: "..as XEDIT and "sed" do ..."
>IIRC, TSO Edit should be included in this list.
>
Not in my list.



On Sun, 10 Jul 2022 16:06:18 +, Seymour J Metz wrote:

>A space in an operator command is the separator between operand and comment. 
>That means that space has to be treated differently from other characters. 
>What the RFE would ask for is to suspend that special treatment for spaces 
>within framiong characters.
>
Within an apostrophe-framed string the special treatment of numerous characters 
such as comma, parentheses, and the apostrophe itself is suspended, perhaps 
using TRT.  It should be simple to add  to the list.

>I don't know how difficult it would be to change MGCR to allow, e.g., /text/, 
>as an alternative to 'text'.
>
I was focusing more on the SDSF API than on MGCR.  But both may need changes, 
for similar
reasons: SDSF to allow an arbitrary string as an operator command; MGCR tp 
allow an arbitrary string as a parameter value.

--
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmy.rocketsoftware.com%2FRocketCommunity%2FRCEmailSupportdata=05%7C01%7Csmetz3%40gmu.edu%7Cb9093384306b44b6369b08da63106e95%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637931219486552276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=aNovhepzOOFX9oFnENhA8ANbaN6vrx6XxGNI8YYSrkA%3Dreserved=0
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fmanage-your-email-preferencesdata=05%7C01%7Csmetz3%40gmu.edu%7Cb9093384306b44b6369b08da63106e95%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637931219486552276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=c7eC9P36It97xMVm2b5pLCJAZWC%2FA4plj4Ssof%2BwQP0%3Dreserved=0
Privacy Policy - 
https://nam11.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.rocketsoftware.com%2Fcompany%2Flegal%2Fprivacy-policydata=05%7C01%7Csmetz3%40gmu.edu%7Cb9093384306b44b6369b08da63106e95%7C9e857255df574c47a0c00546460380cb%7C0%7C0%7C637931219486552276%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7Csdata=zpN4t7STskqcohMreMgA8vzaGq%2BD%2FjGGO6n%2Bs6r4yUI%3Dreserved=0


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Java (Re: Some questions on SYSCALL

[David Crayford]

On 10/07/2022 6:49 pm, Rony wrote:
  
Am 09.07.2022 um 03:15 schrieb David Crayford :

On 8/07/2022 7:17 pm, Rony G. Flatscher wrote:

On 07.07.2022 17:45, David Crayford wrote:
On 7/07/2022 7:53 pm, Rony G. Flatscher wrote:

On 06.07.2022 11:03, Seymour J Metz wrote:

... cut ...

There is one ecosystem that beats Perl, Python and practically any others: 
Java. For every problem domain, for new emerging technologies there are Java 
class libraries which one can take advantage of. As Java classes get compiled 
to intermediate byte code, these Java class libraries can be deployed and used 
immediately on any hardware and any operating system for which a Java virtual 
machine exists.

That's debatable! I'm a full time Java programmer in the last few years and I 
like. We use Spring Boot which is a high quality framework that makes it 
pleasant to use. I would use SB even for a slightly complex command line 
interface. However, the build systems are a bit spotty compared to Node.js, 
Python etc.

Eclipse, NetBeans, IntelliJ, ...

I build Java in IntelliJ using Maven. Also, we use a DevOps pipeline driven by 
Jenkins so using an IDE is out of the question.



Maven is creaking with it's ugly XML pom.xml and

Beauty lies in the eyes of the beholder ...

Maven is not Java and still an incredible boon!

I agree. I just don't like XML. I would rather use Gradle with it's nice Groovy 
DSL where I can drop down and write code for tricky configurations.



Gradle doesn't work very well on some systems.

What does not work for you?

Would you think that the Java multiplatform build system which is done with 
Gradle would be possible, if that were true what you say?

Gradle doesn't work properly on z/OS. First thing I tried was to nobble 
spawning the daemon. I used AOT -Xshareclasses so start up times were not a 
problem. However, Gradle was downloading lots of unwanted dependencies and 
filled up the file system cache. I abandoned it and stuck to Maven.



C# is a far better language then Java.

Excuse me? 

Off the top of my header.

1. Generics done properly with reflection support, not puny type erasure.

Java retains generics information in byte code (for the compiler) after type 
erasure (such that the runtime does not have to recheck after compilation, 
after all the compiler checked already).


2. No checked exceptions

One can use no checked exceptions in Java if one wished. OTOH checked 
exceptions are there and one can take advantage of them.


The JRE uses checked exceptions so you can't avoid them. The damage is 
done. The mess created by checked exceptions became more evident when 
Java 8 introduced Lambda's. There is nothing more ugly than a try/catch 
block in a lambda function. Some people create wrappers but that's just 
bloat. Checked exceptions are widely considered a failed experiment.






3. Unsigned integer types

Not really a problem.


It's a problem for our products. We process a lot of unsigned 64-bit 
integers and perform arithmetic such as division and a BigInteger is not 
acceptable for performance reasons. James Gosling admitted that Java 
didn't implemented unsigned integers as he wanted to keep the language 
simple for new programmers. That's another historical mistake that we 
are paying the price off. Back then Java was designed for very different 
use cases. Writing cryptographic algorithms in Java without an unsigned 
Long is painful. Gosling's nanny state hand holding hasn't aged well. He 
didn't implement operator overloading because he didn't like the way it 
was used for iostreams in C++. Another BIG mistake that makes the 
language awkward to use when doing arithmetic on BigDecimal, BigInteger 
types.


BTW, the very existence of Long.divideUnsigned() is proof enough that 
Java needs unsigned integers. In JDK16 they have optimized the function 
to use an algorithm from Hackers Delight that uses twos-complement 
binary operators. It's a shame we're stuck on JDK8 and the JDK16 code 
uses an unfriendly license for IBM code.




4. Value types

Not really a problem.


Maybe not for you. It's my understanding that you're an educator that 
teaches stuff like OLE and Windows GUI programming using JavaFX. The 
products I work on are back-end systems that process missions of records 
that originate from z/OS data sources. We need to serialize those binary 
records to other formats such as JSON as efficiently as possible. C# has 
struct value types and pointers (unsafe blocks) which would be brilliant 
for this kind of work. IBM realizes this and have implemented 
PackedObjects in their JDK which use intrinsics. Very similar to structs 
and value types in C#. Shame it's not portable!


https://www.ibm.com/docs/en/sdk-java-technology/7.1?topic=poet-packed-objects-2





5. Better support for functional program, LINQ

How so, which bytecodes do you think of?


I'm talking about FP and LINQ which is C# DSL for functional programming 
which looks a bit like SQL.

Re: How do I issue a command with a blank in it?

[Rob Scott]

For what it is worth, SDSF REXX API already accepts an alternate form of input 
for the ISFSLASH verb where you can pass the name of a stem variable that holds 
one or more z/OS operator commands.

For example :

/* REXX */
x=ISFCALLS("ON")
ISFDELAY = 3
mycmd.0  = 2
mycmd.1  = "D A,L"
mycmd.2  = "D T"
address SDSF  "ISFSLASH ("mycmd.") (WAIT)"
do respindex = 1 to ISFULOG.0
  say ISFULOG.respindex
end
exit

Rob Scott
Rocket Software



-Original Message-
From: IBM Mainframe Discussion List  On Behalf Of 
Paul Gilmartin
Sent: 10 July 2022 18:19
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: How do I issue a command with a blank in it?

EXTERNAL EMAIL





On Sun, 10 Jul 2022 11:51:29 -0400, David Spiegel wrote:

>Hi Gil,
>You said: "..as XEDIT and "sed" do ..."
>IIRC, TSO Edit should be included in this list.
>
Not in my list.



On Sun, 10 Jul 2022 16:06:18 +, Seymour J Metz wrote:

>A space in an operator command is the separator between operand and comment. 
>That means that space has to be treated differently from other characters. 
>What the RFE would ask for is to suspend that special treatment for spaces 
>within framiong characters.
>
Within an apostrophe-framed string the special treatment of numerous characters 
such as comma, parentheses, and the apostrophe itself is suspended, perhaps 
using TRT.  It should be simple to add  to the list.

>I don't know how difficult it would be to change MGCR to allow, e.g., /text/, 
>as an alternative to 'text'.
>
I was focusing more on the SDSF API than on MGCR.  But both may need changes, 
for similar
reasons: SDSF to allow an arbitrary string as an operator command; MGCR tp 
allow an arbitrary string as a parameter value.

--
gil

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email to 
lists...@listserv.ua.edu with the message: INFO IBM-MAIN


Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ 
Main Office Toll Free Number: +1 855.577.4323
Contact Customer Support: 
https://my.rocketsoftware.com/RocketCommunity/RCEmailSupport
Unsubscribe from Marketing Messages/Manage Your Subscription Preferences - 
http://www.rocketsoftware.com/manage-your-email-preferences
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy


This communication and any attachments may contain confidential information of 
Rocket Software, Inc. All unauthorized use, disclosure or distribution is 
prohibited. If you are not the intended recipient, please notify Rocket 
Software immediately and destroy all copies of this communication. Thank you.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN