Joined: 22 Sep 2009 Posts: 7 Location: Sydney Australia
Hi
I am trying to setup a point & shoot panel or panel menu that will call
a rex program when the cursor is placed on the point & shoot field , I am
not sure if this is possible, the ISPF manual does not say it can not be
done, but I can not find any examples or write ups on it.
If you have been able to do this, then i would be grateful if you would
share the panel syntax.
Joined: 17 Aug 2007 Posts: 562 Location: Iowa, USA
The Primary Menu can be customized by each user to add a user-created list of point and shoot tasks. It replaces the Calendar or whatever you have in the User area in upper right section of the menu.
You assign the task (REXX, CLIST or PGM) to be started when user puts the cursor there and hits ENTER.
Look in the ISPF UsersGuide Vol II, Chapter 1 for info.
Joined: 01 Sep 2006 Posts: 2594 Location: Silicon Valley
Quote:
just look at one of the ISPF panels (ISR.PRIM) and clone....
I agree ISR@PRIM would be a good example. But it is still non-trivial to do. I suggest also to read the 'Defining the point-and-shoot' section in the ISPF Dialog Developers Guide and Reference.
With regard to calling a rexx program... the point and shoot is merely a way to make a field selection. For example, if you have a menu with three choices, where the user has to type 1, 2, or 3, then the point and shoot simplifies it by providing the numeric value in the correct field. To the rest of the application, it is as if the user had typed the number and pressed the Enter key.
So if you have the capability in your dialog to call a rexx program, you can improve it by adding a point and shoot capability. So my suggestion is to get the call to rexx working first.
You might also get by by using the .CURSOR function in the panel. It will tell you what field the cursor was in.
14 years later, and i still cant find a decent pnts example..
guess I'll have to post one myself or something once i get it,
coz between the IBM terrible manual and that one single example,
I'm really having a hard time..
14 years, perhaps you should have opened a new topic.
Anyway, it can certainly be done, and pretty simple even, using the power of panel REXX as shown in this sample:
Joined: 01 Sep 2006 Posts: 2594 Location: Silicon Valley
re: " that one single example"
It is not clear if you refer to ISR@PRIM as the example...
I found this example in the ISPF Dialog Developer's Guide and
Reference, but IMHO the manual does not provide a good description of what it is supposed to do.
Though, in my opinion, it is also not a simple enough example. It shows two different definitions of point and shoot fields. The panel instruction has text defined as TYPE(PS) and an output field in the panel uses the PAS(ON) attribute. That is, you can click on the word 'defaults' or click on the 'blue' input field.
I was, actually, talking about the ispf manual example.
its all nice and dandy, but has no explanation.
I guess that guys that's been around for some time, got used to the way IBM does their info sharing and manuals and what-not.
As an experienced but "open" guy, whos takling the documentation, history, and MF paradigm for the first time, those methods seem.. somewhat cumbersome.
Like grouping commands by the index, or by the letter, and not by concise topic or purpose.
I guess it's all about getting used to it.
Translating from one paradigm, to another.
Thats the key word here - paradigm shift.
Willy is right. I'll open a new topic.
write a short tut, just to sort things in my head.
I will also just mention the one other example that I found,
that actually hellped me, in stackoverflow - "panel doesnt execute )PNTS Sections". for whomever comes across it.
Joined: 01 Sep 2006 Posts: 2594 Location: Silicon Valley
re: "talking about the ispf manual example"
FYI. There are several manuals and numerous examples. <irony> In complaining about the manuals not being concise, you also were vague in your comment.</irony>
------
The ISPF Dialog Developer's Guide and Reference, SC19-3619-30, has a section for "How to send your comments to IBM". Earlier today, I sent an email asking for improvements on the description of figure 60, which shows the point and shoot usage.
I also do not particularly like the manuals. I have sent numerous "reader's comments" to IBM over the years. They usually are fairly responsive. Though, I did have one instance where an assembler program example abended and was told that "it was only an example". I had to escalate that to get a better response.
If i don't know what exists, what I'm looking for,
and if i cant find it on google, or any form of a-to-z tut,
than its not irony. That's just frustrating.
Thought of explaining myself,
but I just don't see the point.
TL;DR - on ANY system/IDE in the open, in under a month,
you are able to do stuff. It takes under a day, to find a multitude (!)
of tuts, ppl, community, and whatnot.
And they're all willing and welcoming.
They take pride in their community,
and try to grow, and help one-another.
MF has a 50 yo history, dominated by ppl that mostly send you to RTFM.
That is not an answer.
(I'm NOT talking about you specifically, just to clarify.)
In most cases, I don't even know what manuals are out there.
tso, ispf, sdsf, rexx, jobs, jcl.. and you need to grasp them all,
(insert pokemon catch-em-all pun here)
just to hit "hello world" panel,
and that's BEFORE you realize that every sysplex and location,
has its own.. definitions, commands, and.. stuff.
So.. no.
Not irony.
Frustration.
A cold, un-welcoming, harsh, resource poor, closed community,
mostly held together by secret guarding boomers,
In an age of global info-sharing,
gen-z, millennials, and other snowflakes.
Almost 2 years around here, and still feels that way.
But its cool.
I'll be the change, I want to see in others.
How can you face misunderstanding,
when you don't even know what you're looking for?.
Not all. again.
You, Pedro, Willy, and a few others where great help,
to me. specifically.
But you are not the majority.
And you don't set the overall tone.
and the tone is what community is all about..
don't assume he wants the answer.
assume he has no idea what vsam is, or how to write jcl.
maybe he learned Cobol, and hit the mainframe without the background of batch.vs.online, or he's an sql guy that got a request from the boss. or perhaps, like many others - he learns from clear, explained, code examples,
which are close to none existent, and very specific.
I wouldn't bust you RTFM if you'd ask me -
"how do I RACF my user?"
I'd try to explain the concept behind security architecture, maybe hint you to the SAF, and the on-chip architecture,
perhaps try and make the connection to SMF..
In any case, i wouldn't -
"that is not a thing. try again and explain what you want."
how can you explain something you don't know?
I'd try to help. not to show you how stupid you are,
by leveraging how smart I am.
(even though technically - there isn't such a thing.)
and you know what,
if you would ask for something simple like
a "2+2" rexx, I'd give you the code, with a short
explanation, and how to EXEC it,
and I'de explain how to jobcard it,
and point you to the 3 ways, and than to how to find that job. and I would use these words.
not sdsf s;st batch job rtfm ispf tso acronyms.
and if i dont feel like it,
I would rather say nothing, than -
"You're stupid, you don't know anything."
He already knows that.
Thats why he's here.
P.S.
Imagine going to the doc, saying your knee hurts,
and he starts making fun of you, saying -
"Thats not a thing "me knee hurt", come back when
you know whats your problem. oh. and also - here is the entire body encyclopedia pdf. go RTFM."
Agree wholeheartedly. I certainly cannot remember a single instance in my rather long career that someone was helped by being told that s/he was stupid.
Joined: 01 Sep 2006 Posts: 2594 Location: Silicon Valley
My comment about irony was specifically about this statement:
"between the IBM terrible manual and that one single example"
IMHO, in that situation you should have provided concise information with the title and publication number as well as the page that you referenced so that we can all look at it and maybe provide advice.
