On Thu, 21 Jan 2010 15:25:43 -0600, Mark Zelden <[email protected]> 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 ??? Hmmmmmm >> > >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 [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
