|
View previous topic :: View next topic
|
| Author |
Message |
Harvey Sullivan
New User
Joined: 05 Nov 2007
Posts: 19
Location: Monterey CA
|
|
|
|
| Can anyone tell me how to gain addressability to the inital screen returned from CICS (the one that contains the transid)? Or point me to the proper manual in the bookshelf? I can't find anything. |
|
| Back to top |
|
 |
Earl Haigh
Active User
Joined: 25 Jul 2006
Posts: 475
|
|
|
|
not sure I understand the question.
gain addressability from where ? |
|
| Back to top |
|
|
Harvey Sullivan
New User
Joined: 05 Nov 2007
Posts: 19
Location: Monterey CA
|
|
|
|
| For example how to set a pointer to it so I can read the data that is there. something like the address function to get at the cwa or the assign function to gain adressability to the tctua. I have a program that I am converting from macro to command level and the initial screen contained a value (in addtion to the transid) that the program uses. In this case the user enters xxxx,yyyy where xxxx=transid for CICS and YYYY is a value that the program does something with. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Do you need to "READ" a users terminal buffer after the screen has been sent and return that terminal buffer to your own terminal for scrutiny, sort of like an "ISPY" function? 
This sounds like a pre-emptive transaction, which starts asynchronously against a given users terminal.
Because once a transaction (program) sends a screen and issues a CICS RETURN, you're done and their's no addressability available, because it's been returned to the operating system, with the next invocation of that transaction to be launched at that user's terminal, when (for example), they press <Enter>.
Does this sound right 
Regards,
Bill |
|
| Back to top |
|
|
Harvey Sullivan
New User
Joined: 05 Nov 2007
Posts: 19
Location: Monterey CA
|
|
|
|
| Maybe I need to do a receive with"into" to get the transid and the value. It seems after the fact because the real read was already done by CICS. Thanks I will try this. I am not sure I understand the part about ISPY. Also, I thought of a possible jury rigged way to do it by doing a first time return with transid and COMMAREA back to itself. Harvey |
|
| Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006
Posts: 6966
Location: porcelain throne
|
|
|
|
| Quote: |
because the real read was already done by CICS
|
would you care to elaborate on that?
yes, i am being a little sarcastic, since I don't think you know what you are talking about. |
|
| Back to top |
|
|
Harvey Sullivan
New User
Joined: 05 Nov 2007
Posts: 19
Location: Monterey CA
|
|
|
|
| "because the real read was already done by CICS" I meant that the system read your transid and then passed control to your program. Sorry I did not explain myself very well. And yes, I do not know what I am talking about that is why I asked the question. I thought this forum was a place where you could get some help. I guess I was wrong. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Sounds like your background is in Macro/CICS which differs much from Pseudo-Conversational CICS.
Macro/CICS transactions (as you know) were conversational, which might be the cause for these discrepancies.
Can you provide us with a more comprehensive step-by-step and perhaps we can arrive at a better resolution?
HTH....
Regards,
Bill |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
lots of traffic uh...
once upon a time at transaction initiation the programmer would
| Code: |
1234567890123456
.....
..... register equates
..... USING constructs
.....
COPY DFHTCADS
COPY TWAUSER
COPY DFHTCTTE
COPY DFHTIOA
....
.... program initalization
L TCTTEAR,TCAFCAAA
L TIOABAR,TCTTEDA |
and TIOADBA would map the beginning data received by the terminal read
with command level the code is ...
| Code: |
| EXEC CICS RECEIVE ... |
that' s not a true read because terminal read has already been done
it is the new ( command level ) way of doing things to access the terminal buffer
its a way to access the terminal i/o area buffer in order to issue the
with the proper map
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/DFHP4C00/CCONTENTS?SHELF=DFHASJ00&DN=SC34-6819-00&DT=20070612172134 |
|
| Back to top |
|
|
Harvey Sullivan
New User
Joined: 05 Nov 2007
Posts: 19
Location: Monterey CA
|
|
|
|
| Enrico, thanks sooooo much!! I tried this and it worked fine. This is the response and area in the manual I was looking for. You have restored my faith in this board! BTW, the macro code that you showed is very similar to what was in the program (except in PLI) and commented out. |
|
| Back to top |
|
|
Bill O'Boyle
CICS Moderator
Joined: 14 Jan 2008
Posts: 2501
Location: Atlanta, Georgia, USA
|
|
|
|
Enrico,
I haven't been able to find CICS/Macro manuals since the early 90's.
You wouldn't happen to have any copies available as an attachment or maybe, some idea as to where I could get them?
I'd be most appreciative.
Regards,
Bill |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
Hi Bill,
not easy (means impossible) to find,
if You are interested in old IT docs ( hardware and software ) here are two links
www.softlib.org
www.bitsavers.org
Once upon a time there were lots of cics info on
Bob Yelavich web site www.yelavich.com
but when he retired he decided ( sadly ) to throw away everything,
but unless somebody is able to get in touch with him to find out
if he has somewhere old documents and he is willing to share
the IT archaelogists will be out of luck,
and the tone of his web pages hints that he will not be available to cooperate |
|
| Back to top |
|
|
|
|
