|
|
| Author |
Message |
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 7517
Location: 221 B Baker St
|
|
| Back to top |
|
 |
References
|
 Posted: Wed Jun 18, 2008 9:50 am Post subject: Re: |
 |
|
|
|
enrico-sorichetti
Global Moderator
Joined: 14 Mar 2007
Posts: 2562
Location: italy
|
|
| Back to top |
|
|
Kumar Ashok
New User
Joined: 20 Jan 2007
Posts: 29
Location: KOLKATA
|
|
|
|
Thank you all for your valuble inputs. They were very useful. Looking forward for such helps in future.
After developement of my tool VIRTUAL treat for you all 
Regards |
|
| Back to top |
|
|
stodolas
Senior Member
Joined: 13 Jun 2007
Posts: 646
Location: Wisconsin
|
|
|
|
What if someone has their command bar at the top instead of the bottom? What if they have it at the bottom, but tab takes them through the menus also? What if they run this Macro while they are in a split screen view? What if they have the KEYLIST displayed?
Even if you know the resolution, you need to know all of these other things to determine their usable screen size for your macro and what affect any keystrokes you plan on sending have. A good design should be resolution independent.
You should write this in some mainframe side tool. The spool lives on the mainframe and you want the datasets to live on the mainframe after processing. SDSF and CA-View have mechanisms to put spool and job output to datasets. Why use something external to that system to do the processing and just to put the data back on that system.
It sounds like you are trying to replicate what CA-View and other products do and do pretty well. In my shop when you run in a certain job class, the job output is put to CA-View which holds the data in a file and has rules about how long to keep it before rolling it out. |
|
| Back to top |
|
|
Kumar Ashok
New User
Joined: 20 Jan 2007
Posts: 29
Location: KOLKATA
|
|
|
|
The problem is - We run almost 200-300 jobs per day and we have to retain that for future reference. So to retain them in permanent dataset is till now a manula process in our project which takes almost 1-1.5 hrs per day. Using this tool we will be able to complete this process in mere 5-6 mins.
So actually I am not replicating them but using the facility that thay are providing for my pupose.
Regards |
|
| Back to top |
|
|
Pedro
Senior Member
Joined: 01 Sep 2006
Posts: 322
Location: work
|
|
|
|
| Quote: |
| but the problem is still there. |
The problem is in your understanding.
This example:
| Code: |
/* rexx */
Address ISPEXEC
"VGET (ZSCREENW,ZSCREEND)"
Say ZSCREENW ZSCREEND |
is a rexx implementation, but the key point is that ISPF provides variables to determine the screen size. You can use VGET from compiled languages to.
ps. I realize the task is not to determine screen size, but how to save job output. |
|
| Back to top |
|
|
stodolas
Senior Member
Joined: 13 Jun 2007
Posts: 646
Location: Wisconsin
|
|
|
|
| But he is writing this in VB, not REXX, so he can only use the scripting language of his emulator. He would have to run this REXX on the mainframe somehow then capture the output. |
|
| Back to top |
|
|
dick scherrer
Global Moderator
Joined: 23 Nov 2006
Posts: 7517
Location: 221 B Baker St
|
|
|
|
Hello,
| Quote: |
| He would have to run this REXX on the mainframe somehow then capture the output. |
Yes, and i believe this is the new direction being investigated. |
|
| Back to top |
|
|
Pedro
Senior Member
Joined: 01 Sep 2006
Posts: 322
Location: work
|
|
|
|
Sorry, I did not read all of the posts. </blush>
But I do not think you need to know the current size of the screen to determine how many jobs there are. The last part of the panel title has the number of jobs in the list.
| Code: |
Display Filter View Print Options Help
-------------------------------------------------------------------------------
SDSF HELD OUTPUT DISPLAY ALL CLASSES LINES 100,879 LINE 1-11 (15)
COMMAND INPUT ===> SCROLL ===> CSR
NP JOBNAME JOBID CRDATE C FORM FCB DEST RMT NODE TOT-REC O-GR |
In this example, there are 15 jobs.
Your emulator macro should be able to get a screen capture and examine the results.
---or--
If you still want to pursue your current design, just scroll by a fixed amount rather than the variable amount. That is, scroll by 10 instead of by page. |
|
| Back to top |
|
|
Kumar Ashok
New User
Joined: 20 Jan 2007
Posts: 29
Location: KOLKATA
|
|
|
|
@Pedro - Its true that if we scroll by certain amount the there will be no need of knowing the screen size. But there are two limitations
1) My emulator doesn't provide the information in the way you shown rather its something like..
-------------------------------------------------------- IOF Job List Menu ---------------------------------------( 61 )-----------
COMMAND ===> SCROLL ===> CURSOR
----------------------------------------------------------- Output Jobs -----------------------------------------------------------
-------JOBNAME--JOBID---ACT-STAT-OWNER----DEST/DEVICE-------RECS-HELD-DAY--TIME-PAGES-HELD-ALLOC---RLSE CLASS-SECLABEL-------------
so there is no information on the jobs.
2) I am a mainframe guy with very limited knowledge of scripting language and to learn a complete language in limited time that too for a small tool is overkill I guess.
Yes I was able to capture the info running REXX EXEC so I will ne using that info for my further improvement in this tool
Thanks again thanks for your help
Regards, |
|
| Back to top |
|
|
|
|
