View previous topic :: View next topic
|
Author |
Message |
henry888
New User
Joined: 21 Sep 2009 Posts: 51 Location: china
|
|
|
|
I am making a tool for xmitting data and what I want to implement is that keeping screen locked when xmitting data is being executed,and after that,screen should be released for use.
does anyone get the knowledge or any idea?
thanks a lot. |
|
Back to top |
|
|
valyk
Active User
Joined: 16 Apr 2008 Posts: 104 Location: South Carolina
|
|
|
|
Redisplay the panel with the "CONTROL DISPLAY LOCK" function.
Code: |
ADDRESS ISPEXEC
'CONTROL DISPLAY LOCK'
'DISPLAY PANEL(PANLNAME)' |
Then to unlock:
Code: |
ADDRESS ISPEXEC
'CONTROL DISPLAY REFRESH'
'DISPLAY PANEL(PANLNAME)' |
|
|
Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009 Posts: 1306 Location: Vilnius, Lithuania
|
|
|
|
If you're creating an XMIT file in foreground REXX, your screen will be locked anyway, so why not KISS? |
|
Back to top |
|
|
henry888
New User
Joined: 21 Sep 2009 Posts: 51 Location: china
|
|
|
|
no,the XMIT is not in foreground,it is actually in background using TSO XMIT command written by REXX.
Thanks valyk for your guide,
my situation is like this:the XMIT action is a loop process,when the first dataset is being XMITed,a message panel must be shown that the XMIT is going on,and should keep locked status until all the datasets are XMITed.
My my question is:if the message panel needs to keep locked,how the REXX codes to be executed in the following for 2nd,3rd...dataset?(if you don't put action to panel like pressing PFkeys,the rexx codes will not be triggerred to excute...)
if I am wrong please correct me...
And anyone could help to give a solution to my situation? |
|
Back to top |
|
|
prino
Senior Member
Joined: 07 Feb 2009 Posts: 1306 Location: Vilnius, Lithuania
|
|
|
|
As I already wrote, "If you're creating an XMIT file in foreground REXX, your screen will be locked anyway, so why not KISS?"
Now do you understand? |
|
Back to top |
|
|
dbzTHEdinosauer
Global Moderator
Joined: 20 Oct 2006 Posts: 6966 Location: porcelain throne
|
|
|
|
Quote: |
no,the XMIT is not in foreground,it is actually in background using TSO XMIT command written by REXX. |
prino,
henry does not understand the difference between foreground and background. |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2547 Location: Silicon Valley
|
|
|
|
Henry, please read the ISPF Services Guide for the information about 'CONTROL DISPLAY LOCK'. I think the manual will answer your question. |
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
Pedro wrote: |
Henry, please read the ISPF Services Guide for the information about 'CONTROL DISPLAY LOCK'. I think the manual will answer your question. |
What, no pointers to the "ISPF Services Guide"? |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2547 Location: Silicon Valley
|
|
Back to top |
|
|
CICS Guy
Senior Member
Joined: 18 Jul 2007 Posts: 2146 Location: At my coffee table
|
|
|
|
Thanks for the pointer, but I really hate the 'infoserver' format and the pointer is not that specific to the "'CONTROL DISPLAY LOCK'" in the "ISPF Services Guide" you were implying. |
|
Back to top |
|
|
henry888
New User
Joined: 21 Sep 2009 Posts: 51 Location: china
|
|
|
|
thanks everyone for your replies
and a new question :when after executing TRANSMIT command successfully,the sender will receive some information like:
DMTNTR147I Sent file 2904 (7280) on link....
10.44.15 TSU17468 $HASP546 XXXXXXX (TSU07280 FROM XXXXXXX ) SYSTEM OUTPUT RECEIVED AT XXXXXXX CN(INTERNAL)
and these information sometimes can confuse the user,how can I let these information not appear in screen? |
|
Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009 Posts: 2481 Location: Netherlands, Amstelveen
|
|
|
|
I think any user likes to know someone did send something. |
|
Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007 Posts: 10873 Location: italy
|
|
|
|
and anyway the DMTNTR147I message is not a zOs message
is a message generated by a RSCS node somewhere in the network telling that the file has been successfully processed by RSCS |
|
Back to top |
|
|
Pedro
Global Moderator
Joined: 01 Sep 2006 Posts: 2547 Location: Silicon Valley
|
|
|
|
Quote: |
I really hate the 'infoserver' format |
The link I provided has both book and PDF formats. I use the PDF formatted books. If you search for 'CONTROL DISPLAY LOCK', it finds the correct section. |
|
Back to top |
|
|
|