Re: Error : DMSITS135S Maximum SVC depth 200 has been exceeded
Hi, Sorry for my late response. Thanks Stephen, Les and Mike for responding! Yes, there were two linked disks that had the same exec along with the A disk where it was present too. When I remove one of the disks, it works fine. But we have had this setup for a long time i.e. apart from A disk, we have a test code disk and production code disk linked to this server. So not sure why it's happenin g now. A new thing that has happened and that I haven't mentioned so far is that earlier the rexx codes were run using rexx interpretor and now it has compiled versions on the two linked disks except A disk where it is still non-compiled version. But if I remove the non-compiled version from A disk, it still fails. I a m reluctant to conclude that its due to the compiled rexx as the same is working in other vmserve servers. Regards, Amar On Tue, 19 Apr 2011 10:02:35 -0500, Mike Walter mike.wal...@aonhewitt.co m wrote: Amar, Could you logon to the service machine running VMSERVE, stop VMSERVE, an d then run the command that was running when you experienced the failure? If it still fails the same way, you will evidence that VMSERVE is not causing the problem, and can look elsewhere. An alternative if you don't want to stop VMSERVE: from another ID, link to all the disks that VMSERVE has accessed and run the same failing command. If the same failure occurs, you can diagnose, correct, and test the solution with affecting VMSERVE, then move the fix into production. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Amar Moh amar_...@yahoo.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/19/2011 06:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Error : DMSITS135S Maximum SVC depth 200 has been exceeded Hi, We are running VMSERVE, the application server/scheduler on a z/VM CP/CM S system. Recently, it started giving this error every time we make a program run through VMSERVE. I am not very experienced in z/VM so any help is appreciated! System : z/VM Version 5 Release 2.0, Service Level 0801 (64-bit) WWVM ESA CMS 15 012 VMSERVE starts fine but as soon as it runs a program, VMSERVE crashes an d ends with this error, DMSITS135S Maximum SVC depth 200 has been exceeded. DMSITS135S Maximum SVC depth 200 has been exceeded. It probably means : The CMS system does not allow the nesting level of SVCs to exceed ''. But not sure what can be done to fix this. Regards, Amar The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mail s are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deem ed to have accepted these risks if you communicate with us by e-mail. =
Re: Error : DMSITS135S Maximum SVC depth 200 has been exceeded
Isn't this simply an EXEC that calls itself over over again. Or, dirty execs that do not use ADDRESS COMMAND and by accident call an EXEC instead of the built-in CMS command. 2011/5/2 Amar Moh amar_...@yahoo.com Hi, Sorry for my late response. Thanks Stephen, Les and Mike for responding! Yes, there were two linked disks that had the same exec along with the A disk where it was present too. When I remove one of the disks, it works fine. But we have had this setup for a long time i.e. apart from A disk, we have a test code disk and production code disk linked to this server. So not sure why it's happening now. A new thing that has happened and that I haven't mentioned so far is that earlier the rexx codes were run using rexx interpretor and now it has compiled versions on the two linked disks except A disk where it is still non-compiled version. But if I remove the non-compiled version from A disk, it still fails. I am reluctant to conclude that its due to the compiled rexx as the same is working in other vmserve servers. Regards, Amar On Tue, 19 Apr 2011 10:02:35 -0500, Mike Walter mike.wal...@aonhewitt.com wrote: Amar, Could you logon to the service machine running VMSERVE, stop VMSERVE, and then run the command that was running when you experienced the failure? If it still fails the same way, you will evidence that VMSERVE is not causing the problem, and can look elsewhere. An alternative if you don't want to stop VMSERVE: from another ID, link to all the disks that VMSERVE has accessed and run the same failing command. If the same failure occurs, you can diagnose, correct, and test the solution with affecting VMSERVE, then move the fix into production. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Amar Moh amar_...@yahoo.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/19/2011 06:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Error : DMSITS135S Maximum SVC depth 200 has been exceeded Hi, We are running VMSERVE, the application server/scheduler on a z/VM CP/CMS system. Recently, it started giving this error every time we make a program run through VMSERVE. I am not very experienced in z/VM so any help is appreciated! System : z/VM Version 5 Release 2.0, Service Level 0801 (64-bit) WWVM ESA CMS 15 012 VMSERVE starts fine but as soon as it runs a program, VMSERVE crashes and ends with this error, DMSITS135S Maximum SVC depth 200 has been exceeded. DMSITS135S Maximum SVC depth 200 has been exceeded. It probably means : The CMS system does not allow the nesting level of SVCs to exceed ''. But not sure what can be done to fix this. Regards, Amar The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. = -- Kris Buelens, IBM Belgium, VM customer support
Re: Error : DMSITS135S Maximum SVC depth 200 has been exceeded
It looks like something else on that linked disk has changed. Perhaps the linking process (VMLINK?) is doing something different, like EXECLOADing something that is now tripping you up. As I said before: Look at the log file and the console spool file for clues. It should be quite obvious. Les Amar Moh wrote: Hi, Sorry for my late response. Thanks Stephen, Les and Mike for responding! Yes, there were two linked disks that had the same exec along with the A disk where it was present too. When I remove one of the disks, it works fine. But we have had this setup for a long time i.e. apart from A disk, we have a test code disk and production code disk linked to this server. So not sure why it's happenin g now. A new thing that has happened and that I haven't mentioned so far is that earlier the rexx codes were run using rexx interpretor and now it has compiled versions on the two linked disks except A disk where it is still non-compiled version. But if I remove the non-compiled version from A disk, it still fails. I a m reluctant to conclude that its due to the compiled rexx as the same is working in other vmserve servers. Regards, Amar On Tue, 19 Apr 2011 10:02:35 -0500, Mike Walter mike.wal...@aonhewitt.co m wrote: Amar, Could you logon to the service machine running VMSERVE, stop VMSERVE, an d then run the command that was running when you experienced the failure? If it still fails the same way, you will evidence that VMSERVE is not causing the problem, and can look elsewhere. An alternative if you don't want to stop VMSERVE: from another ID, link to all the disks that VMSERVE has accessed and run the same failing command. If the same failure occurs, you can diagnose, correct, and test the solution with affecting VMSERVE, then move the fix into production. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Amar Moh amar_...@yahoo.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/19/2011 06:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Error : DMSITS135S Maximum SVC depth 200 has been exceeded Hi, We are running VMSERVE, the application server/scheduler on a z/VM CP/CM S system. Recently, it started giving this error every time we make a program run through VMSERVE. I am not very experienced in z/VM so any help is appreciated! System : z/VM Version 5 Release 2.0, Service Level 0801 (64-bit) WWVM ESA CMS 15 012 VMSERVE starts fine but as soon as it runs a program, VMSERVE crashes an d ends with this error, DMSITS135S Maximum SVC depth 200 has been exceeded. DMSITS135S Maximum SVC depth 200 has been exceeded. It probably means : The CMS system does not allow the nesting level of SVCs to exceed ''. But not sure what can be done to fix this. Regards, Amar The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mail s are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deem ed to have accepted these risks if you communicate with us by e-mail. =
Re: Error : DMSITS135S Maximum SVC depth 200 has been exceeded
On Monday, 05/02/2011 at 11:32 EDT, Amar Moh amar_...@yahoo.com wrote: But if I remove the non-compiled version from A disk, it still fails. I am reluctant to conclude that its due to the compiled rexx as the same is working in other vmserve servers. There is something else causing the problem, as CMS doesn't care if an exec is compiled or not. You can use the SVCTRACE ON command to see what's happening. HELP SVCTRACE for details. (CP SPOOL 00E TO * before you start so that you can use RDRLIST and PEEK to look at the trace.) Alan Altmark z/VM and Linux on System z Consultant IBM System Lab Services and Training ibm.com/systems/services/labservices office: 607.429.3323 mobile; 607.321.7556 alan_altm...@us.ibm.com IBM Endicott
Error : DMSITS135S Maximum SVC depth 200 has been exceeded
Hi, We are running VMSERVE, the application server/scheduler on a z/VM CP/CMS system. Recently, it started giving this error every time we make a progr am run through VMSERVE. I am not very experienced in z/VM so any help is appreciated! System : z/VM Version 5 Release 2.0, Service Level 0801 (64-bit) WWVM ESA CMS 15 012 VMSERVE starts fine but as soon as it runs a program, VMSERVE crashes and ends with this error, DMSITS135S Maximum SVC depth 200 has been exceeded. DMSITS135S Maximum SVC depth 200 has been exceeded. It probably means : The CMS system does not allow the nesting level of SV Cs to exceed ''. But not sure what can be done to fix this. Regards, Amar
Re: Error : DMSITS135S Maximum SVC depth 200 has been exceeded
Amar, we just had this happen on a totally different program. What was happening was the user had created an EXEC on there A disk that was identical to the name on another disk. When they run their EXEC, it basically kept calling itself causing recursion and exceeding available SVC's So, look for duplicate file names. Steve -Original Message- From: The IBM z/VM Operating System [mailto:IBMVM@LISTSERV.UARK.EDU] On Behalf Of Amar Moh Sent: Tuesday, April 19, 2011 7:09 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Error : DMSITS135S Maximum SVC depth 200 has been exceeded Hi, We are running VMSERVE, the application server/scheduler on a z/VM CP/CMS system. Recently, it started giving this error every time we make a progr am run through VMSERVE. I am not very experienced in z/VM so any help is appreciated! System : z/VM Version 5 Release 2.0, Service Level 0801 (64-bit) WWVM ESA CMS 15 012 VMSERVE starts fine but as soon as it runs a program, VMSERVE crashes and ends with this error, DMSITS135S Maximum SVC depth 200 has been exceeded. DMSITS135S Maximum SVC depth 200 has been exceeded. It probably means : The CMS system does not allow the nesting level of SV Cs to exceed ''. But not sure what can be done to fix this. Regards, Amar
Re: Error : DMSITS135S Maximum SVC depth 200 has been exceeded
Look at it's log file and console spool file to see what it was doing when the error occurred. The message is typical for an exec that executes something that executes the exec, as Stephen pointed out. If you've configured VMSERVE properly it is fairly unusual for it to suddenly change it's behavior unless a disk it is linked to has introduced something new. Of course this also assumes that all the EXECs that you've given it to use follow the Good Rexx Coding Practices rules. Les Amar Moh wrote: Hi, We are running VMSERVE, the application server/scheduler on a z/VM CP/CMS system. Recently, it started giving this error every time we make a progr am run through VMSERVE. I am not very experienced in z/VM so any help is appreciated! System : z/VM Version 5 Release 2.0, Service Level 0801 (64-bit) WWVM ESA CMS 15 012 VMSERVE starts fine but as soon as it runs a program, VMSERVE crashes and ends with this error, DMSITS135S Maximum SVC depth 200 has been exceeded. DMSITS135S Maximum SVC depth 200 has been exceeded. It probably means : The CMS system does not allow the nesting level of SV Cs to exceed ''. But not sure what can be done to fix this. Regards, Amar
Re: Error : DMSITS135S Maximum SVC depth 200 has been exceeded
Amar, Could you logon to the service machine running VMSERVE, stop VMSERVE, and then run the command that was running when you experienced the failure? If it still fails the same way, you will evidence that VMSERVE is not causing the problem, and can look elsewhere. An alternative if you don't want to stop VMSERVE: from another ID, link to all the disks that VMSERVE has accessed and run the same failing command. If the same failure occurs, you can diagnose, correct, and test the solution with affecting VMSERVE, then move the fix into production. Mike Walter Aon Corporation The opinions expressed herein are mine alone, not my employer's. Amar Moh amar_...@yahoo.com Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 04/19/2011 06:09 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Error : DMSITS135S Maximum SVC depth 200 has been exceeded Hi, We are running VMSERVE, the application server/scheduler on a z/VM CP/CMS system. Recently, it started giving this error every time we make a program run through VMSERVE. I am not very experienced in z/VM so any help is appreciated! System : z/VM Version 5 Release 2.0, Service Level 0801 (64-bit) WWVM ESA CMS 15 012 VMSERVE starts fine but as soon as it runs a program, VMSERVE crashes and ends with this error, DMSITS135S Maximum SVC depth 200 has been exceeded. DMSITS135S Maximum SVC depth 200 has been exceeded. It probably means : The CMS system does not allow the nesting level of SVCs to exceed ''. But not sure what can be done to fix this. Regards, Amar The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
