View previous topic :: View next topic |
Author |
Message |
meetrb Beginner
Joined: 24 Nov 2003 Posts: 40 Topics: 15
|
Posted: Fri May 07, 2004 8:31 am Post subject: Continous JOB in IOF |
|
|
Hi,
When I go into the IOF menu I can see a job that runs as long as I am logged in. This job executes the program IKJEFT01. I have gone through the links in this forum that describes the functionality of the program.
I am interested in knowing as to the functionality of the job i.e the purpose of running that job. Does the job process any of the commands that we execute in ISPF.
Thanks,
meetrb |
|
Back to top |
|
|
kolusu Site Admin
Joined: 26 Nov 2002 Posts: 12376 Topics: 75 Location: San Jose
|
Posted: Fri May 07, 2004 9:51 am Post subject: |
|
|
Meetrb,
I am not familiar with IOF, but we have sdsf here and I see a job which is running as long as I am logged on. Upon logon this job gets execueted allocating system CLIST, REXX, Panel, MESSAGE, SKELTON, TABLE libraries.
The procedure can be found in SYS1.TSOPROCS, but I am not really sure if is the same name for all the shops.
Type in DDLIST on the command promand and you will see all the current dataset allocations.
You can type SAVE to generate a Clist for the allocation and you can see which datasets are allocated to your sysexec and sysproc
Hope this helps...
Cheers
Kolusu _________________ Kolusu
www.linkedin.com/in/kolusu |
|
Back to top |
|
|
Maton_Man Beginner
Joined: 30 Jan 2004 Posts: 123 Topics: 0
|
Posted: Sun May 09, 2004 10:26 pm Post subject: |
|
|
The job you see is your TSO session. Your ISPF commands will be processed by this job. If I am not mistaken your JOBID will be TSUnnnnn rather than JOBnnnnn. TSU = Time Sharing User, ie TSO user. _________________ My opinions are exactly that. |
|
Back to top |
|
|
meetrb Beginner
Joined: 24 Nov 2003 Posts: 40 Topics: 15
|
Posted: Tue May 11, 2004 3:29 am Post subject: |
|
|
Hi All,
Thank you for all the replies.
Maton_Man wrote: | The job you see is your TSO session. Your ISPF commands will be processed by this job. If I am not mistaken your JOBID will be TSUnnnnn rather than JOBnnnnn. TSU = Time Sharing User, ie TSO user. |
How does the job receive the commands entered by the user. Does it have anything to do with the IKJEFT01 program?
Thanks,
Meetrb |
|
Back to top |
|
|
Maton_Man Beginner
Joined: 30 Jan 2004 Posts: 123 Topics: 0
|
Posted: Tue May 11, 2004 6:54 pm Post subject: |
|
|
You can read all about IKJEFT01 in the TSO manuals. Look in TSO/E Customization under APPENDIX1.1 Appendix A. Executing the Terminal Monitor Program.
Simplistically, your IKJEFT01 session monitors what you input via your terminal and passes that input to the appropriate programs for processing and then passes you back the results. _________________ My opinions are exactly that. |
|
Back to top |
|
|
Mike Beginner
Joined: 03 Dec 2002 Posts: 114 Topics: 0 Location: Sydney, Australia
|
Posted: Tue May 11, 2004 7:13 pm Post subject: |
|
|
IKJEFT01 is what is generally known as TSO (Time Share Option). Basically when you logon you are effectively running a job (although it is classed differently by JES etc) that has the ddname SYSTSIN and SYSTSPRT allocated to your terminal/emulator.
If you are in native TSO (i.e. see the ready prompt, you may not be able to, as opposed to in ISPF) you can directly enter TSO commands such as HELP (lists further TSO commands).
The majority of people rarely use native TSO nowadays, instead freindly interfaces run under TSO (or perhaps not, as in the case of ROSCOE) such as ISPF/PDF. However in ISPF you can still issue TSO commands, from the command line by prefixing the command with TSO or from option 6 (assuming the ISPF defaults) without the need to prefix the command wit TSO. Thus you can type TSO HELP on a command line, you will see the results are output line by line and require enter to be pressed after a screen load of lines and at the end of the output.
You could look at it this way, you type something, such as TSO HELP at the command line. ISPF basically grabs this and then writes it to SYSTSIN, IKFET01 reads it, and then writes the resultant output to SYSTSPRT which is your terminal.
You could simulate IKJEFT01 by writing a program that reads 80 byte data records (I think) via a ddname, e.g. INDD and reformats it and writes it to another ddname, e.g. OUTDD. Note that the program would loop (hopefully issuing a system wait so it doesn't hog the CPU). Once you have compiled the load module (it could also be a Rexx program). You can then issue the TSO commands to allocate INDD * OUTDD to the terminal (e.g. ALLOC INDD DA(*) and ALLOC OUTDD DA(*) if memory serves me well). Invoke the program and you can read and write data to the terminal. Note that I haven't fully checked this so I may have got a few things wrong, but it should give you the basic idea. Obviously IKJEFT01 is a lot more complicated that this though. _________________ Regards,
Mike. |
|
Back to top |
|
|
meetrb Beginner
Joined: 24 Nov 2003 Posts: 40 Topics: 15
|
Posted: Wed May 12, 2004 1:45 am Post subject: |
|
|
Thank you all for the replies.
It was very useful.
Thanks,
Meetrb |
|
Back to top |
|
|
|
|