Re: WLM and FTP GETS From Open Systems
>>Nevertheless, the rule you posted is assigning SYSSTC to each an >>every file transfer. > >No, only the FTP daemon. I think you are assuming I am using >_BPX_JOBNAME because I mentioned it. We don't. My bad, yes I was assuming you're using _BPX_JOBNAME for the ftpd. >Are you saying I can do this: > > More ===> > Qualifier ---Class >ActionType Name Start Service Report > DEFAULTS: OMVSOMVS > 1 TN CTG* ___SYSSTC CICS > 1 TN FTP* ___SYSSTC NETWORK > 2UI MYUSERID ___ GOD GOD_ > 1 TN ETCRC* ___SYSSTC SYSTEM > 1 TN ETCINIT* ___ SYSSTC SYSTEM > >And FTPs initiated by MYUSERID will go to service class GOD but the >rest of the OMVS work by MYUSERID will go to OMVS? I don't think >so. The TN is MYUSERID, not FTP*. Or am I misunderstanding. My example was again assuming that _BPX_JOBNAME=FTPsomething is set for ftpd, then all sessions will run with TN=FTPsomething. And only then will the subrule catch the userids listed. In your case, your ftp session will run with service class OMVS (assuming the above shonw rules are all there are). Unfortunately, the OMVS subsystem section in the classification rules doesn't give you more than TN and UI (plus some less usefull). I always thought it to be difficult to setup some good rules for all that forked/spawned UNIX work. To distinguish between interactive users and system work, you need to be able clearly to distinguish TN and UI. If you don't force jobnames to adhere to some site specific rules, what inhibits a user to submit a batch job using the jobname of a server (say CTGMYJOB) and have all work happily run the same serviced class (SYSSTC in this example). -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Mon, 25 Jan 2010 13:12:05 -0600, Dave Kopischke wrote: >On Thu, 21 Jan 2010 16:36:56 -0600, Mark Zelden > wrote: > >>2) Can you screen print the OMVS classification rules from WLM. It should >>like something like this one (from a sandbox plex here): >> >>Subsystem Type . : OMVSFold qualifier names? Y (Y or N) >>Description . . . OMVS Classification >> > Here's a follow up I added the OMVS subsystem type and moved my FTP classification rule to it. FTP's are being assigned the proper service class now. I've also assigned a proper default to the type as well. I'll keep an eye on it to ensure everything is classifying properly, but it looks good right now. Thanks again for all your help -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Mon, 25 Jan 2010 14:27:16 -0600, Peter Hunkeler wrote: >>>ftp's children run under the userid with which the >>>remote user logged in; and the jobname is derived from that >>>userid as well. You can't catch ftpd's child processes >>>with ftpd's userid. >>> >> >> >> >>No, but you can do this to force the same jobname for all by doing >>something like this in the ftp server proc: > >Right and I'm sorry again for the incomplete post from this morning. >It is exactly this _BPX_JOBNAME option that I was vaguely remembering >all over a sudden and that I wanted to look up first. > >Nevertheless, the rule you posted is assigning SYSSTC to each an every >file transfer. No, only the FTP daemon. I think you are assuming I am using _BPX_JOBNAME because I mentioned it. We don't.FTPs run under a different classification in OMVS or the default of OMVS. In my sandbox sysplex where I copied from, they run in OMVS. > >>ActionType Name StartService Report >> DEFAULTS: OMVSOMVS >> 1 TN CTG* ___ SYSSTC CICS >> 1 TN FTP* ___ SYSSTC NETWORK >> 1 TN ETCRC* ___ SYSSTC SYSTEM >> 1 TN ETCINIT* ___ SYSSTC SYSTEM > >Is this really what you want? I'd either assign a different jobname to >the ftpd servers (_BPX_JOBNAME=FTPCLIEN) and then assign a separate >service class to the "clients" (I know they are server processes as per >client/server convention :-) See my comments above. > >You may even want to prefer some userids in case you've got some automated >transfers: > >ActionType Name StartService Report > DEFAULTS: OMVSOMVS > 1 TN CTG* ___ SYSSTC CICS > 1 TN FTP* ___ SYSSTC NETWORK > 1 TN FTPCLIEN ___ FTPSTD NETWORK > 2 UI SYSXFER FTPHIGH NETWORK > 1 TN ETCRC* ___ SYSSTC SYSTEM > 1 TN ETCINIT* ___ SYSSTC SYSTEM > > >-- Are you saying I can do this: More ===> Qualifier ---Class ActionType Name StartService Report DEFAULTS: OMVSOMVS 1 TN CTG* ___ SYSSTC CICS 1 TN FTP* ___ SYSSTC NETWORK 2UI MYUSERID ___GOD GOD_ 1 TN ETCRC* ___ SYSSTC SYSTEM 1 TN ETCINIT* ___ SYSSTC SYSTEM And FTPs initiated by MYUSERID will go to service class GOD but the rest of the OMVS work by MYUSERID will go to OMVS? I don't think so. The TN is MYUSERID, not FTP*. Or am I misunderstanding. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Mon, 25 Jan 2010 14:27:16 -0600, Peter Hunkeler wrote: >Nevertheless, the rule you posted is assigning SYSSTC to each an every >file transfer. > This is exactly the confusion that got me. These spawned tasks run as started tasks but are not originated as such and therefore are not assigned the service class defined within the STC group. Lacking an OMVS subsystem type, they default to the interactive default service class. And adding a pattern to the interactive list won't allow you to assign a service class to the task either. They will get the interactive default service class and that's it. Apparently you need the OMVS subsystem type in order to assign service classes to these tasks. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
>>ftp's children run under the userid with which the >>remote user logged in; and the jobname is derived from that >>userid as well. You can't catch ftpd's child processes >>with ftpd's userid. >> > > > >No, but you can do this to force the same jobname for all by doing >something like this in the ftp server proc: Right and I'm sorry again for the incomplete post from this morning. It is exactly this _BPX_JOBNAME option that I was vaguely remembering all over a sudden and that I wanted to look up first. Nevertheless, the rule you posted is assigning SYSSTC to each an every file transfer. >ActionType Name StartService Report > DEFAULTS: OMVSOMVS > 1 TN CTG* ___ SYSSTC CICS > 1 TN FTP* ___ SYSSTC NETWORK > 1 TN ETCRC* ___ SYSSTC SYSTEM > 1 TN ETCINIT* ___ SYSSTC SYSTEM Is this really what you want? I'd either assign a different jobname to the ftpd servers (_BPX_JOBNAME=FTPCLIEN) and then assign a separate service class to the "clients" (I know they are server processes as per client/server convention :-) You may even want to prefer some userids in case you've got some automated transfers: ActionType Name StartService Report DEFAULTS: OMVSOMVS 1 TN CTG* ___ SYSSTC CICS 1 TN FTP* ___ SYSSTC NETWORK 1 TN FTPCLIEN ___ FTPSTD NETWORK 2 UI SYSXFER FTPHIGH NETWORK 1 TN ETCRC* ___ SYSSTC SYSTEM 1 TN ETCINIT* ___ SYSSTC SYSTEM -- Peter Hunkeler Credit Suisse -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 16:36:56 -0600, Mark Zelden wrote: >2) Can you screen print the OMVS classification rules from WLM. It should >like something like this one (from a sandbox plex here): > >Subsystem Type . : OMVSFold qualifier names? Y (Y or N) >Description . . . OMVS Classification > Sorry it has taken so long to respond I checked my definitions and there is no OMVS subsystem type. So then I hit the manuals again and found it there. The text desciption of the interactive workload says UNIX System Services is included. This pretty much qualifies as an "Oh Sh1t" moment I'll add that and see how things work. Thanks again -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Mon, 25 Jan 2010 09:16:17 +0100, Hunkeler Peter (KIUP 4) wrote: >It's been a while...but this is what I seem to remember >(too lazy to RTFM right now): > >ftp's children run under the userid with which the >remote user logged in; and the jobname is derived from that >userid as well. You can't catch ftpd's child processes >with ftpd's userid. > No, but you can do this to force the same jobname for all by doing something like this in the ftp server proc: //FTPD EXEC PGM=&MODULE,REGION=4096K,TIME=NOLIMIT, //PARM=('POSIX(ON) ALL31(ON)', // 'ENVAR("_BPX_JOBNAME=myftp")/&PARMS') And then create a WLM rule for that under OMVS. Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
You can use the _BPX_JOBNAME variable in a STDENV DDNAME for the FTPD proc. for example if you are setting _BPX_JOBNAME=FTPDA then all client will be named (forked) FTPDAn. I hope this helps Regards, Jacky Hofbauer zCost Management www.zcostmanagement.com -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
Please excuse me for sending that incomplete post. I had the intention to "save" instead of "send" right know because I wanted to first confirm a statement I was about to make -- Peter Hunkeler CREDIT SUISSE AG -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
It's been a while...but this is what I seem to remember (too lazy to RTFM right now): ftp's children run under the userid with which the remote user logged in; and the jobname is derived from that userid as well. You can't catch ftpd's child processes with ftpd's userid. >Subsystem Type . : OMVSFold qualifier names? Y (Y or N) >Description . . . OMVS Classification > >Action codes: A=After C=CopyM=Move I=Insert rule >B=BeforeD=Delete row R=Repeat IS=Insert Sub-rule > More ===> > Qualifier ---Class >ActionType Name StartService Report > DEFAULTS: OMVSOMVS > 1 TN CTG* ___ SYSSTC CICS > 1 TN FTP* ___ SYSSTC NETWORK > 1 TN ETCRC* ___ SYSSTC SYSTEM > 1 TN ETCINIT* ___ SYSSTC SYSTEM I assume ftpd is initially started as started task (STC) with a STC name like FTPD. This will be classified by the STC rules. Very quickly, ftpd will fork() and the new process will then be classified by the above rule (second line). Later on, a user logs into ftp and ftpd will fork another process and switch to the users Peter Hunkeler CREDIT SUISSE AG Information Technology Print Engineering, KIUP 4 Uetlibergstrasse 231 CH-8070 Zurich Phone +41 (0)44 332 2697 Fax +41 (0)44 333 1464 http://www.credit-suisse.com -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Mark Zelden Sent: Thursday, January 21, 2010 11:37 PM To: IBM-MAIN@bama.ua.edu Subject: Re: WLM and FTP GETS From Open Systems On Thu, 21 Jan 2010 16:01:55 -0600, Dave Kopischke wrote: >On Thu, 21 Jan 2010 15:25:43 -0600, Mark Zelden > wrote: > >... >>>One thing I just noticed though, when I swapped the service class over to >>>STC, I didn't change the Workload Name within the service class. Would >that >>>possibly keep it from assigning properly ??? Hmm >>> >> >>What does "swapping the SC over to STC" mean? > >Instead of making up a new service class, I just added a rule under STC to >assign the existing service class to the JOB name. There is a workload name in >the service class definition though. I did not change that though, so I'm not >sure if that might have kept it from being assigned. > >> >>Are you confusing the FTP daemon's SC with the process that gets started >>when someone initiates the FTP? Once the FTP is initiated, do you see >>the process in an SDSF PS screen or have you tried doing a unix ps display >>like "ps -Af" (do it as superuser) to see what is says is the userid? >> > >No, I see the daemon and see other daemons spawn as connections and >commands are run. I found the user ID with the Display line command in SDSF >PS. I displayed the process to ensure I had the names right - FTPPROD. There >is a started task that I believe is associated with the OMVS process. The >started task is what actually receives the default service class that keeps the >FTP from running. Once I manually set the service class on the started task, >the FTP process finishes. > 2 things: 1) Initiate the FTP. After you initiate it, please do a "D A,userid" and post that. 2) Can you screen print the OMVS classification rules from WLM. It should like something like this one (from a sandbox plex here): Subsystem Type . : OMVSFold qualifier names? Y (Y or N) Description . . . OMVS Classification Action codes: A=After C=CopyM=Move I=Insert rule B=BeforeD=Delete row R=Repeat IS=Insert Sub-rule More ===> Qualifier ---Class ActionType Name StartService Report DEFAULTS: OMVSOMVS 1 TN CTG* ___ SYSSTC CICS 1 TN FTP* ___ SYSSTC NETWORK 1 TN ETCRC* ___ SYSSTC SYSTEM 1 TN ETCINIT* ___ SYSSTC SYSTEM 3) Screen print the service class specified under DEFAULTS. For example: Service Class Name . . . . . : OMVS Description . . . . . . . . . OMVS Service Workload Name . . . . . . . . OMVS (name or ?) Base Resource Group . . . . . (name or ?
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 16:01:55 -0600, Dave Kopischke wrote: >On Thu, 21 Jan 2010 15:25:43 -0600, Mark Zelden > wrote: > >... >>>One thing I just noticed though, when I swapped the service class over to >>>STC, I didn't change the Workload Name within the service class. Would >that >>>possibly keep it from assigning properly ??? Hmm >>> >> >>What does "swapping the SC over to STC" mean? > >Instead of making up a new service class, I just added a rule under STC to >assign the existing service class to the JOB name. There is a workload name in >the service class definition though. I did not change that though, so I'm not >sure if that might have kept it from being assigned. > >> >>Are you confusing the FTP daemon's SC with the process that gets started >>when someone initiates the FTP? Once the FTP is initiated, do you see >>the process in an SDSF PS screen or have you tried doing a unix ps display >>like "ps -Af" (do it as superuser) to see what is says is the userid? >> > >No, I see the daemon and see other daemons spawn as connections and >commands are run. I found the user ID with the Display line command in SDSF >PS. I displayed the process to ensure I had the names right - FTPPROD. There >is a started task that I believe is associated with the OMVS process. The >started task is what actually receives the default service class that keeps the >FTP from running. Once I manually set the service class on the started task, >the FTP process finishes. > 2 things: 1) Initiate the FTP. After you initiate it, please do a "D A,userid" and post that. 2) Can you screen print the OMVS classification rules from WLM. It should like something like this one (from a sandbox plex here): Subsystem Type . : OMVSFold qualifier names? Y (Y or N) Description . . . OMVS Classification Action codes: A=After C=CopyM=Move I=Insert rule B=BeforeD=Delete row R=Repeat IS=Insert Sub-rule More ===> Qualifier ---Class ActionType Name StartService Report DEFAULTS: OMVSOMVS 1 TN CTG* ___ SYSSTC CICS 1 TN FTP* ___ SYSSTC NETWORK 1 TN ETCRC* ___ SYSSTC SYSTEM 1 TN ETCINIT* ___ SYSSTC SYSTEM 3) Screen print the service class specified under DEFAULTS. For example: Service Class Name . . . . . : OMVS Description . . . . . . . . . OMVS Service Workload Name . . . . . . . . OMVS (name or ?) Base Resource Group . . . . . (name or ?) Cpu Critical . . . . . . . . . NO(YES or NO) Specify BASE GOAL information. Action Codes: I=Insert new period, E=Edit period, D=Delete period. ---Period--- -Goal- Action # Duration Imp. Description __ __1 40002Execution velocity of 40 __2 4Execution velocity of 15 Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 15:25:43 -0600, Mark Zelden wrote: ... >>One thing I just noticed though, when I swapped the service class over to >>STC, I didn't change the Workload Name within the service class. Would that >>possibly keep it from assigning properly ??? Hmm >> > >What does "swapping the SC over to STC" mean? Instead of making up a new service class, I just added a rule under STC to assign the existing service class to the JOB name. There is a workload name in the service class definition though. I did not change that though, so I'm not sure if that might have kept it from being assigned. > >Are you confusing the FTP daemon's SC with the process that gets started >when someone initiates the FTP? Once the FTP is initiated, do you see >the process in an SDSF PS screen or have you tried doing a unix ps display >like "ps -Af" (do it as superuser) to see what is says is the userid? > No, I see the daemon and see other daemons spawn as connections and commands are run. I found the user ID with the Display line command in SDSF PS. I displayed the process to ensure I had the names right - FTPPROD. There is a started task that I believe is associated with the OMVS process. The started task is what actually receives the default service class that keeps the FTP from running. Once I manually set the service class on the started task, the FTP process finishes. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 15:17:36 -0600, Mark Zelden wrote: ... >>I don't know then. I just double checked and I have the User ID correct. It's >>all upper case. And it takes the default service class no matter what. > >The OMVS default service class? > Yes, the default for INT which includes OMVS. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 14:21:34 -0600, Dave Kopischke wrote: >On Thu, 21 Jan 2010 14:05:35 -0600, Staller, Allan >wrote: > >>FTP has an OMVS component. Use the OMVS section for workload >>classification. >>You might also want to review the default service class for each >>workload classification. >> > >That's how I had it set up. That's what Ted suggested too. Since it wasn't >assigning the proper service class, I changed it to the STC group. I just >changed it back and defined a user ID group and made sure I typed the user >ID in all upper case. Getting ready to try it again and see what happens. > >One thing I just noticed though, when I swapped the service class over to >STC, I didn't change the Workload Name within the service class. Would that >possibly keep it from assigning properly ??? Hmm > What does "swapping the SC over to STC" mean? Are you confusing the FTP daemon's SC with the process that gets started when someone initiates the FTP? Once the FTP is initiated, do you see the process in an SDSF PS screen or have you tried doing a unix ps display like "ps -Af" (do it as superuser) to see what is says is the userid? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 13:50:38 -0600, Dave Kopischke wrote: >On Thu, 21 Jan 2010 19:41:49 +, Ted MacNEIL >wrote: > >>>This is how I set it up. Doesn't work. Unless the user ID is being munged >>somewhere ??? I'll look at that a little closer. >> >>It worked for me with HOD, TCP/IP, TN3270, and FTP(d) many years ago. >>- > >I don't know then. I just double checked and I have the User ID correct. It's >all upper case. And it takes the default service class no matter what. The OMVS default service class? Mark -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:mark.zel...@zurichna.com z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
Have you, by some happenstance, ever issued a manual command to change the class? I've found that WLM will sometimes hold the result of the last manual command. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Dave Kopischke Sent: Thursday, January 21, 2010 1:51 PM To: IBM-MAIN@bama.ua.edu Subject: Re: WLM and FTP GETS From Open Systems On Thu, 21 Jan 2010 19:41:49 +, Ted MacNEIL wrote: >>This is how I set it up. Doesn't work. Unless the user ID is being munged >somewhere ??? I'll look at that a little closer. > >It worked for me with HOD, TCP/IP, TN3270, and FTP(d) many years ago. >- I don't know then. I just double checked and I have the User ID correct. It's all upper case. And it takes the default service class no matter what. Hm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 14:05:35 -0600, Staller, Allan wrote: >FTP has an OMVS component. Use the OMVS section for workload >classification. >You might also want to review the default service class for each >workload classification. > That's how I had it set up. That's what Ted suggested too. Since it wasn't assigning the proper service class, I changed it to the STC group. I just changed it back and defined a user ID group and made sure I typed the user ID in all upper case. Getting ready to try it again and see what happens. One thing I just noticed though, when I swapped the service class over to STC, I didn't change the Workload Name within the service class. Would that possibly keep it from assigning properly ??? Hmm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 14:05:44 -0600, Hal Merritt wrote: >Have you, by some happenstance, ever issued a manual command to change the class? > >I've found that WLM will sometimes hold the result of the last manual command. > Like a: RESET FTPPROD,SRVCLASS=?? kind of manual change ??? Or something specific to WLM ??? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
FTP has an OMVS component. Use the OMVS section for workload classification. You might also want to review the default service class for each workload classification. HTH, I am trying to adjust a WLM service class for an FTP GET process coming from another host. The process is assigned a service class from the interactive workload group. I added a new transaction name to assign a different service class in the interactive group and it was ignored. Then I noticed that the process actually runs as a started task. So I swapped the transaction name rule to the STC group. Still didn't assign the proper service class. The process is picking up the default interactive group service class. This is meant for TSO users, so it has 2nd and 3rd period defined. The FTP usually runs right at the start of our batch cycle, so there aren't many resources available. When the process drops into 2nd and 3rd period, it basically hangs. If I manually increase the service class, it runs fine and completes fairly quickly. Any ideas on how to properly assign a service class to a process like this ??? -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 19:41:49 +, Ted MacNEIL wrote: >>This is how I set it up. Doesn't work. Unless the user ID is being munged >somewhere ??? I'll look at that a little closer. > >It worked for me with HOD, TCP/IP, TN3270, and FTP(d) many years ago. >- I don't know then. I just double checked and I have the User ID correct. It's all upper case. And it takes the default service class no matter what. Hm -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
>This is how I set it up. Doesn't work. Unless the user ID is being munged somewhere ??? I'll look at that a little closer. It worked for me with HOD, TCP/IP, TN3270, and FTP(d) many years ago. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
Also, make sure you get the case correct. We got burned once when it wasn't folded to uppercase and didn't match. Bobby Herring System Programmer Texas Farm Bureau Ins Waco, TX CONFIDENTIALITY STATEMENT: The foregoing message (including attachments) is covered by the Electronic Communication Privacy Act, 18 U.S.C. sections 2510-2521, and is CONFIDENTIAL. If you believe that it has been sent to you in error, do not read it. If you are not the intended recipient, you are hereby notified that any retention, dissemination, distribution, or copying of this communication is strictly prohibited. Please reply to the sender that you have received the message in error, then delete it. Thank you. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Dave Kopischke Sent: Thursday, January 21, 2010 1:34 PM To: IBM-MAIN@bama.ua.edu Subject: Re: [IBM-MAIN] WLM and FTP GETS From Open Systems On Thu, 21 Jan 2010 18:58:48 +, Ted MacNEIL wrote: >>Any ideas on how to properly assign a service class to a process like >this ??? > >1. Find the userid (USS) used by FTP. >2. Go to the OMVS section of your policy. >3. Use a UI (instance) matching the userid, and assign that to your appropriate Service Class. > This is how I set it up. Doesn't work. Unless the user ID is being munged somewhere ??? I'll look at that a little closer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
On Thu, 21 Jan 2010 18:58:48 +, Ted MacNEIL wrote: >>Any ideas on how to properly assign a service class to a process like >this ??? > >1. Find the userid (USS) used by FTP. >2. Go to the OMVS section of your policy. >3. Use a UI (instance) matching the userid, and assign that to your appropriate Service Class. > This is how I set it up. Doesn't work. Unless the user ID is being munged somewhere ??? I'll look at that a little closer. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: WLM and FTP GETS From Open Systems
>Any ideas on how to properly assign a service class to a process like this ??? 1. Find the userid (USS) used by FTP. 2. Go to the OMVS section of your policy. 3. Use a UI (instance) matching the userid, and assign that to your appropriate Service Class. - Too busy driving to stop for gas! -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
WLM and FTP GETS From Open Systems
Greetings, I am trying to adjust a WLM service class for an FTP GET process coming from another host. The process is assigned a service class from the interactive workload group. I added a new transaction name to assign a different service class in the interactive group and it was ignored. Then I noticed that the process actually runs as a started task. So I swapped the transaction name rule to the STC group. Still didn't assign the proper service class. The process is picking up the default interactive group service class. This is meant for TSO users, so it has 2nd and 3rd period defined. The FTP usually runs right at the start of our batch cycle, so there aren't many resources available. When the process drops into 2nd and 3rd period, it basically hangs. If I manually increase the service class, it runs fine and completes fairly quickly. Any ideas on how to properly assign a service class to a process like this ??? Thanks, Dave K. -- This e-mail transmission may contain information that is proprietary, privileged and/or confidential and is intended exclusively for the person(s) to whom it is addressed. Any use, copying, retention or disclosure by any person other than the intended recipient or the intended recipient's designees is strictly prohibited. If you are not the intended recipient or their designee, please notify the sender immediately by return e-mail and delete all copies. OppenheimerFunds may, at its sole discretion, monitor, review, retain and/or disclose the content of all email communications. == -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html