|
Maybe the following I don't think there's much difference. Group jobs have the *GDA, which is 512 bytes common to all of them. But I prefer separate emulations, usually, becasue they can all be live, doing something productive. Group jobs are suspended - can't get to one until what you are doing is done. Maybe the following from the Work Management manual can help - Group Job Performance Tips - Using process access groups (PAGs) with group jobs has performance advantages. Each group job (active or suspended) requires approximately 1KB of dedicated main storage in the machine pool. Thus, the number of group jobs that are allowed to be active is a consideration. However, if main storage is not limited, this may be a good way to gain the benefits of separate process access groups (PAGs). This also allows you to avoid the overhead caused by repetitive opening of files and reestablishing environments, and to avoid excessive interactions to access common functions. See also "Process Access Groups" on page 264. - The effect on the system for a large number of suspended jobs is normally small if the dedicated main storage requirement is not a factor. - When a TFRGRPJOB command runs and a new job must be started, the overhead involved is roughly the same as signing on to the system. When the command is run and the group job is already started, the overhead required is roughly the same as using the transfer to a secondary job option on the System Request menu when the secondary job is already active. - If a group job is to be run with any frequency, it is desirable to prevent it from ending. That is, do not end the program, but issue a TFRGRPJOB command to prevent job starting each time the group job function is needed. - The SETATNPGM command causes the current display to be saved when the Attention key is pressed, and to be restored when the Attention key-handling-program ends. This is roughly the same as using of the System Request menu and has a more noticeable effect on remote workstations. - The controls on the number of jobs active in the system (the MAXJOBS parameter on the CRTSBSD command) are not affected by the number of group jobs active at any time. - All system values that control the creation of job structures (QACTJOB and QADLACTJ, and QTOTJOB and QADLTOTJ) are affected; these values may need to be increased to allow for the addition of group jobs. At 04:34 PM 4/29/02 -0500, you wrote: >I would like to know the differences in resource requirements between >running 16 group jobs, vs. 16 interactive jobs from the same PC... > >Thanks, >Trevor Perry >looksoftware.com > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com >Before posting, please take a moment to review the archives >at http://archive.midrange.com/midrange-l.
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
