|
the difference is the wrkstn entry ( addwse ). an interactive job starts by signing onto a display that is allocated to a sbs thru its wrkstn entry. such a job will show INT on WrkActJob. A batch job starts thru the SbmJob cmd. my theory is that a batch job, started by the SbmJob cmd, can open a dspf and interact with a user via a display terminal. such a job on a server model will be considered a batch job and will not cause CFINTxx to consume cpu. Steve -----Original Message----- From: Walden H. Leverich <WaldenL@TechSoftInc.com> To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com> Date: Monday, April 23, 2001 5:37 PM Subject: RE: batch job that uses a dspf. >OK, I'm curious, what is an "Interactive Subsystem?" I know we _think_ of >QINTER as interactive and QBATCH as batch, but there isn't any real >difference between these, is there? I'm not suggesting that the two >subsystems are configured the same, but just that the _only_ difference is >one of configuration. If I configured QINTER to have the QBATCH jobq and >QBATCH to have all the workstations wouldn't QBATCH be my "interactive" >subsystem and "QINTER" be my batch? > >In short, a subsystem is a subsystem, period. There is no difference between >"interactive" and "batch" subsystems, no? > >-Walden > >-----Original Message----- >From: bruce-list@netburg.net [mailto:bruce-list@netburg.net] >Sent: Sunday, April 22, 2001 11:52 AM >To: MIDRANGE-L@midrange.com >Subject: Re: batch job that uses a dspf. > > >Check out the "Interactive vs. Batch" thread currently going. Here is an >excerpt: > > >On Fri, Apr 20, 2001, 5:04:14 PM GMT Jim Damato wrote: > > >The link provided by Nathan Andelin defines the types of jobs that will be >classified as interactive: > >o All 5250 sessions >o Any green screen interface >o Telnet or 5250 DSPT workstations >o 5250/HTML workstation gateway >o PCs using 5250 emulation >o Interactive program debugging >o PC Support/400 work station function >o RUMBA/400 >o Screen scrapers >o Interactive subsystems >o Twinax printer jobs >o BSC 3270 emulation >o 5250 emulation > >(end of excerpt) > >The point is that traditionally, we have worried about the interactive >subsystem vs. the batch subsystem. Now, due to IBM's restrictions on >interactive jobs, we have to look at what the system is going to limit due >to being classified as interactive. So having a display file is one factor, >but not the only one, as the list above shows. > >Bruce Hobbs > > >On Sun, Apr 22, 2001, 6:01:11 AM GMT Steve Richter wrote: > > >>Alexei, >>are you sure that interactive is any job that uses a dspf ? >> >>the ibm doc on this subject says: >>"In general, the Type column of the Work with Active Jobs (WRKACTJOB) >>command will tell you which jobs are considered interactive (type = INT). >>These are all jobs that were initiated by signing on at a 5250 display >>device." >> >>other evidence to the contrary: >> >>1. an interactive sbs can be defined as a sbs that contains a workstation >>entry. ( addwse ). >>2. ibm supplied interactive cmds like strpdm and wrkactjob and cmd >prompting >>do not work in a batch job that acquires its device. Even when you override >>the ibm supplied dspf to the acquired device. >> >>question to all: do batch jobs that are submitted to an interactive sbs on >a >>server model cause the CFINT job to run and degrade performance just as an >>interactive job? >> >>Steve >> >>-----Original Message----- >>From: Alexei Pytel <pytel@us.ibm.com> >>To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> >>Date: Friday, April 20, 2001 9:55 PM >>Subject: Re: batch job that uses a dspf. >> >> >>> >>>It does not matter whether job type is interactive or batch. What matters >>>is whether job uses display I/O. >>>All interactive jobs use it by definition, but if batch job acquires a >>>display and tries to do display I/O, it will immediately become an >>>"interactive" in a sense, with all the consequences. >>> >>> Alexei Pytel >>> >>> >>> >>> >>> "Steve Richter" >>> <srichter@AutoCoder To: >><MIDRANGE-L@midrange.com> >>> .com> cc: >>> Sent by: Subject: batch job that >>uses a dspf. >>> owner-midrange-l@mi >>> drange.com >>> >>> >>> 04/20/2001 02:36 AM >>> Please respond to >>> MIDRANGE-L >>> >>> >>> >>> >>> >>>On a server system, does a batch job that runs a pgm that writes to a dspf >>>run a full server speed, or does it run in the interactive penalty box and >>>cause the cpu wasting CFINT job to run? >>> >>>To illustrate my question ... >>> >>>The code at the end of the email will create a cmd, dspf and cl pgm. The >>>pgm, cmd and dspf are all named BatMenu. >>> >>>The cl pgm will prompt a menu on the display and execute the selected >>>option. >>> >>>The cmd is used to call the cl pgm with its one parameter: This parm >>>contains the name of the display device to write the menu to. >>> >>>The cl pgm is intended to run in a batch job. So it will OvrDspf its dspf >>>to the device name passed in parm 1. >>> OvrDspf BatMenu Dev(&Device) >>> >>>To run the pgm, do the following: >>> 1. Get the device name of a display that has a signon screen ( not >>>signed on ) >>> 2. SBMJOB CMD(BATMENU DEVICE(sssss)) JOB(BATMENU) >>> >>>When I run this on my system, the job type of the job is BATCH. >>> >>>My question is: On a server model, does this BATCH job that writes to a >>>display terminal run at full server speed or does it run in the >interactive >>>penalty box and cause the cpu wasting CFINT job to run? >>> >>>The code follows. I have included it in case what I am asking is not >clear. >>>Or it might be usefull as tutorial on the use of the Device parm of the >>>OvrDspf cmd. >>> >>>Thanks for the help, >>>Steve Richter >>> >>> >>>1. Add the following to a srcmbr BatMenu in qgpl/qcmdsrc: >>> CMD PROMPT('Batch job display test') >>> PARM KWD(DEVICE) TYPE(*CHAR) LEN(10) + >>> PROMPT('Device name') >>>2. Create the command: >>> CrtCmd qgpl/batmenu qgpl/qcmdsrc batmenu >>> >>>3. Add the following source code to dspf srcmbr BatMenu in qgpl/qddssrc: >>> A R BATMENU1 >>> A 2 2'MENU' >>> A 4 2' 1. SNDMSG' >>> A 10 2'90. SIGNOFF' >>> A 12 2'OPTION:' >>> A OPTN 2 0B 12 10EDTCDE(Z) >>>4. Create the dspf: >>> CrtDspf qgpl/batmenu qgpl/qddssrc batmenu >>> >>>5. Add the following source code to clp srcmbr BatMenu in qgpl/qclsrc: >>> PGM PARM(&DEVICE) >>> DCL VAR(&DEVICE) TYPE(*CHAR) LEN(10) >>> >>> DCLF FILE(BATMENU) >>> DCL VAR(&JOB) TYPE(*CHAR) LEN(10) >>> DCL VAR(&USER) TYPE(*CHAR) LEN(10) >>> DCL VAR(&JOBTYPE) TYPE(*CHAR) LEN(1) >>> >>> OVRDSPF FILE(BATMENU) DEV(&DEVICE) >>>/* OVERRIDE YOUR APPLICATIONS DISPLAY FILES HERE. */ >>> >>> B1: DO >>> CHGVAR VAR(&OPTN) VALUE(0) >>> SNDRCVF RCDFMT(BATMENU1) >>> IF COND(&OPTN *EQ 90) THEN(GOTO CMDLBL(E1)) >>> >>> IF COND(&OPTN *EQ 1) THEN(DO) >>> RTVJOBA JOB(&JOB) USER(&USER) TYPE(&JOBTYPE) >>> SNDMSG MSG('Job' *BCAT &JOB *BCAT 'is job type' + >>> *BCAT &JOBTYPE) TOUSR(&USER) >>> >>> ENDDO >>> >>> GOTO CMDLBL(B1) >>> E1: ENDDO >>> >>> ENDPGM >>>6. Create the cl pgm >>> CrtClPgm qgpl/batmenu qgpl/qclsrc >>> >>> >>> >>> >>>+--- >>>| This is the Midrange System Mailing List! >>>| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >>>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >>>| To unsubscribe from this list send email to >>MIDRANGE-L-UNSUB@midrange.com. >>>| Questions should be directed to the list owner/operator: >>david@midrange.com >>>+--- >>> >> >>+--- >>| This is the Midrange System Mailing List! >>| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >>| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >>| To unsubscribe from this list send email to >MIDRANGE-L-UNSUB@midrange.com. >>| Questions should be directed to the list owner/operator: >david@midrange.com >>+--- >> >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: >david@midrange.com >+--- >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
