PCE long wait for JES2 command
Hi listers, We have a Lpar (not in sysplex), every time when we shutdown/warmstart JES2 in IPL, we have a command $PLINE(*)/$SLINE(*), we will get: *$HASP9203 LONG PCE DISPATCH 188 DURATION-000:00:17.76 PCE-COMM EXIT-NONE JOB ID-NONE COMMAND-$PLINE(*) $HASP003 RC=(25),P LINE(*) - NO SELECTABLE DEVICE(S) FOUND $HASP9301 JES2 MAIN TASK ALERTS CLEARED I checked, we don't have any LINE defined, why this command would spend so much time? Not sure if MASDEF related, MASDEF DORMANCY=(100,500), HOLD=0, LOCKOUT=1000, Anyother field I should check? Thanks! -- Cobe Xu Best Regards --- zOS Performance Capacity Analyst E2E Performance Analyst Email: cob...@gmail.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: PCE long wait for JES2 command
If you have no lines, why are you issuing the command(s) at all? Check and see if there are any line(nn) statements in you init deck and only start/stop that number of lines, or remove the commands entirely if no line(nn) statements are present. I just checked the manual and the range for line(*) is 1-65535. Since you specified LINE(*) in your command, it will have to check 64K lines. This is bound to take a while. This is most likely not caused by you MASDEF parameters. HTH, snip We have a Lpar (not in sysplex), every time when we shutdown/warmstart JES2 in IPL, we have a command $PLINE(*)/$SLINE(*), we will get: *$HASP9203 LONG PCE DISPATCH 188 DURATION-000:00:17.76 PCE-COMM EXIT-NONE JOB ID-NONE COMMAND-$PLINE(*) $HASP003 RC=(25),P LINE(*) - NO SELECTABLE DEVICE(S) FOUND $HASP9301 JES2 MAIN TASK ALERTS CLEARED I checked, we don't have any LINE defined, why this command would spend so much time? Not sure if MASDEF related, MASDEF DORMANCY=(100,500), HOLD=0, LOCKOUT=1000, /snip -- 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: PCE long wait for JES2 command
Thanks, Allan..that make sense to me... I checked the jes2 init deck, there's no LINE(nnn) statement... On Wed, Jan 27, 2010 at 9:48 PM, Staller, Allan allan.stal...@kbm1.comwrote: If you have no lines, why are you issuing the command(s) at all? Check and see if there are any line(nn) statements in you init deck and only start/stop that number of lines, or remove the commands entirely if no line(nn) statements are present. I just checked the manual and the range for line(*) is 1-65535. Since you specified LINE(*) in your command, it will have to check 64K lines. This is bound to take a while. This is most likely not caused by you MASDEF parameters. HTH, snip We have a Lpar (not in sysplex), every time when we shutdown/warmstart JES2 in IPL, we have a command $PLINE(*)/$SLINE(*), we will get: *$HASP9203 LONG PCE DISPATCH 188 DURATION-000:00:17.76 PCE-COMM EXIT-NONE JOB ID-NONE COMMAND-$PLINE(*) $HASP003 RC=(25),P LINE(*) - NO SELECTABLE DEVICE(S) FOUND $HASP9301 JES2 MAIN TASK ALERTS CLEARED I checked, we don't have any LINE defined, why this command would spend so much time? Not sure if MASDEF related, MASDEF DORMANCY=(100,500), HOLD=0, LOCKOUT=1000, /snip -- 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 -- Cobe Xu Best Regards --- zOS Performance Capacity Analyst E2E Performance Analyst Email: cob...@gmail.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
