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, <snip> 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 ??? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
