|
-----Original Message----- From: Scott Mildenberger [mailto:Smildenber@Washcorp.com] Sent: Thursday, April 05, 2001 3:44 PM To: 'MIDRANGE-L@midrange.com' Subject: RE: Code/400 Jeff, Are you running over TCP/IP? We are running the V4R5 version and don't need the STRCODE session most of the time. I believe the previous version also supported this. I think you may only need the STRCODE session when debugging. This doesn't answer your question but could solve it anyway. Scott Mildenberger > -----Original Message----- > From: Bull, Jeff [mailto:BullJ1@Midas-Kapiti.com] > Sent: Thursday, April 05, 2001 7:46 AM > To: 'MIDRANGE-L@midrange.com' > Subject: Code/400 > > > To the Midrange-L University of Life > > Programmers at my site have recently started using Code/400; > the programmer > opens a CA/400 session on the AS/400 and executes the STRCODE > command; the > session goes input-inhibited (the 'X - System' status > displays) and stays > that way until l they are ready to sign off. > > To me this seems like a cock-eyed way of doing things, but > heck - who am I > to argue with IBM system designers. > > My problem : performance data with response times in excess > of 999 seconds; > I have to report on these statistics, which make it appear > that the system > performance is shot to blazes; in reality the response times > of the 'normal > busy users' are still very good (.4s), though the average > with these long > responses included has gone as high as 14.9s. > > Any suggestions on how I can (a) exclude these STRCODE jobs > or transactions > from the stats ? > or (b) use some > other methodology > to connect the STRCODE users with a non-interactive session ? > > I have given a little thought to how I could run these sessions in a > *SHRPOOLn, i.e. not *INTERACT, though I'm not convinced > enough to try it. > > Kind regards, > Jeff Bull. > Senior Support Consultant > Certified IBM AS/400 System Administrator > Midas Kapiti International Ltd +--- | 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.