SDSF ENQ (was Who has enqueue on ISPF table?)

[Bob Bridges]

I found the ENQ command in the SDSF/REXX documentation. But when I try to issue any form of the ENQ command in any SDSF panel (not from REXX), it claims "INVALID COMMAND". Is there an authorization issue I should look into, or are we using an old version of SDSF, or what?

---
Bob Bridges, robhb...@gmail.com, cell 336 382-7313

/* Every contrition for sin is apt to encourage a not-quite-charitable wish that other people should exhibit a similar contrition. -Charles Williams (1886-1945) */

-----Original Message-----
From: Bob Bridges <robhb...@gmail.com>
Sent: Thursday, March 11, 2021 16:06

2) They do use SDSF at this installation. Where would I look up this ENQ command? Is it one of the REXX-interface features?

-----Original Message-----
From: TSO REXX Discussion List <TSO-...@VM.MARIST.EDU> On Behalf Of ITschak Mugzach
Sent: Thursday, March 11, 2021 15:25

There are several easy ways to know who holds the table:

1. ISPEXEC TBSTAT will tell who last updated the table.
2. SDSF ENQ *; filter major eq SPFEDIT (minor is the table library name).
3. operator command

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LIST...@VM.MARIST.EDU with the message: INFO TSO-REXX

[David Spiegel]

Hi Bob,
If your ESM is ACF2, it could be TSO Command Limiting.

Regards,
David

> .

[Steve Beaver]

Yes it does

My apologies for the finger-checks

Sent from my iPhone

> On Mar 11, 2021, at 21:04, David Spiegel <dspie...@hotmail.com> wrote:
> Hi Bob,

[James Campbell]

If you have TASID, option 3 allows you to look at current ENQs.

And, if you don't
https://www.ibm.com/support/pages/tasid-v521-tool

James Campbell



--
This email has been checked for viruses by AVG.
https://www.avg.com

[Don Leahy]

ISPF has a QUERYENQ service that is easy to use.

On Fri, Mar 12, 2021 at 23:29 James Campbell <jacamp...@gmail.com>
wrote:

[Bob Bridges]

I tried that first, on someone else's recommendation. But I couldn't get a response from SDSF, and when I try the ENQ command manually (which I read about in the documentation), ISPF responds "invalid command", or something like that; it's been a few days now. I'm guessing there's an authorization issue, which I should be able to solve because I'm a security admin but so far I can't figure out where the authorization might be lacking.

But really I like the ISPF solution better, since the REXX I'm working on is written for REXX/ISPF in the first place. (Why bring in another environment?)

---
Bob Bridges, robhb...@gmail.com, cell 336 382-7313

/* Remember that you are ~always~ your own boss. The company that hires you is your client. You are selling your time and expertise, if you have any. */

-----Original Message-----
From: TSO REXX Discussion List <TSO-...@VM.MARIST.EDU> On Behalf Of Don Leahy
Sent: Tuesday, March 16, 2021 19:46

ISPF has a QUERYENQ service that is easy to use.

--- On Fri, Mar 12, 2021 at 23:29 James Campbell <jacamp...@gmail.com> wrote:
> If you have TASID, option 3 allows you to look at current ENQs.
>
> And, if you don't
> https://www.ibm.com/support/pages/tasid-v521-tool

[Lionel Dyck]

Try this - some code I put together when I experimented with queryenq

/* rexx */
arg prefix
Address ISPExec
major = '*'
minor = prefix
save = 'Z'random(99999)
if right(minor,1) /= '*' then minor = minor'*'
"QueryENQ Qname(major) Rname(minor) Save("save") XSYS Table(xyz)"
qrc = rc
'TBEnd xyz'
say 'rc:' qrc
if qrc = 2 then say 'Datasets under hlq:' prefix 'are open and enqueued.'
if sysvar('syspref') = '' then save = sysvar('sysuid')'.'save
"browse dataset("save".enqlist)"
Address TSO
'delete' save'.enqlist'

_________________________________________________________________
Lionel B. Dyck <sdg>
Senior Software Engineer
21st Century Software
940 West Valley Road
Suite 1604
Wayne, PA 19087
www.21stcenturysoftware.com

lio...@21csw.com
(800) 555-6845 x610
(610) 710-4832 – Office

From the Leaders in Data Stewardship™

THIS E-MAIL MAY CONTAIN PRIVILEGED, CONFIDENTIAL, COPYRIGHTED, OR OTHER LEGALLY PROTECTED INFORMATION. IF YOU ARE NOT THE INTENDED RECIPIENT (EVEN IF THE E-MAIL ADDRESS ABOVE IS YOURS), YOU MAY NOT USE, COPY, OR RE-TRANSMIT IT. IF YOU HAVE RECEIVED THIS BY MISTAKE PLEASE NOTIFY US BY RETURN E-MAIL, THEN DELETE. THANK YOU.

This e-mail (including any attachments) may contain privileged, confidential, proprietary, private, copyrighted, or other legally protected information. The information is intended to be for the use of the individual or entity designated above. If you are not the intended recipient (even if the e-mail address above is yours), please notify us by return e-mail immediately, and delete the message and any attachments. Any disclosure, reproduction, distribution or other use of this message or any attachments by an individual or entity other than the intended recipient is prohibited.

[Itschak Mugzach]

Bob, it is a release depended. I have it on 2.3 and 2.4

בתאריך יום ד׳, 17 במרץ 2021, 18:04, מאת Bob Bridges ‏<robhb...@gmail.com
>:

[Seymour J Metz]

QUERYENQ is an ISPF service, not a command valid in a command line. A search on "ispf QUERYENQ" will get you relevant links.


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

________________________________________
From: TSO REXX Discussion List [TSO-...@VM.MARIST.EDU] on behalf of Bob Bridges [robhb...@GMAIL.COM]
Sent: Wednesday, March 17, 2021 12:03 PM

To: TSO-...@VM.MARIST.EDU
Subject: Re: [TSO-REXX] SDSF ENQ (was Who has enqueue on ISPF table?)

I tried that first, on someone else's recommendation. But I couldn't get a response from SDSF, and when I try the ENQ command manually (which I read about in the documentation), ISPF responds "invalid command", or something like that; it's been a few days now. I'm guessing there's an authorization issue, which I should be able to solve because I'm a security admin but so far I can't figure out where the authorization might be lacking.

But really I like the ISPF solution better, since the REXX I'm working on is written for REXX/ISPF in the first place. (Why bring in another environment?)

---
Bob Bridges, robhb...@gmail.com, cell 336 382-7313

[Bob Bridges]

Sorry, I think I misspoke. It's been a week or two, but in the below I
believe I was talking about interacting with SDSF, and it would have been
SDSF (not ISPF) that claimed the ENQ command was invalid.

---
Bob Bridges, robhb...@gmail.com, cell 336 382-7313

/* When I face an issue of great import that cleaves both constituents and
colleagues, I always take the same approach. I engage in deep deliberation
and quiet contemplation. I wait to the last available minute and then I
always vote with the losers. Because, my friend, the winners never remember
and the losers never forget. -Sen. Everett Dirksen */

-----Original Message-----
From: TSO REXX Discussion List <TSO-...@VM.MARIST.EDU> On Behalf Of Seymour
J Metz
Sent: Sunday, March 21, 2021 12:32

QUERYENQ is an ISPF service, not a command valid in a command line. A search
on "ispf QUERYENQ" will get you relevant links.

________________________________________
From: TSO REXX Discussion List [TSO-...@VM.MARIST.EDU] on behalf of Bob
Bridges [robhb...@GMAIL.COM]
Sent: Wednesday, March 17, 2021 12:03 PM

I tried that first, on someone else's recommendation. But I couldn't get a
response from SDSF, and when I try the ENQ command manually (which I read
about in the documentation), ISPF responds "invalid command", or something
like that; it's been a few days now. I'm guessing there's an authorization
issue, which I should be able to solve because I'm a security admin but so
far I can't figure out where the authorization might be lacking.

But really I like the ISPF solution better, since the REXX I'm working on is
written for REXX/ISPF in the first place. (Why bring in another
environment?)