John next ice cream is for me The problem with the q da details What´s about a q da draining, a q da space efficient... Etc Do we pass through the same code ?
Envoyé de mon iPhone > Le 2 juil. 2015 à 14:25, "John P. Hartmann" <[email protected]> a écrit : > > Hello, Alain. > > I do not understand your question. You are issuing a CP command. > > Anyways, you need to redirect the PMR to CP. Either it sets the wrong length > on the diagnose or it fails to process the final device address. Pipes > faithfully reports what CP returns. > > That is, there is not (today at least) a problem with either version of CMS > Pipelines. > >> On 07/02/2015 02:20 PM, Alain Benvéniste wrote: >> No problem ! >> John, a subsidiary question: does it affect any commands where we can put >> ranges ? >> >> Ready; T=0.01/0.01 14:14:26 >> trace diag 8 cmd d psw g >> Ready; T=0.01/0.01 14:14:48 >> pipe cp q da details 8000-8FFF 660A !> a a a >> -> 0180BACE EX 44001000 01855FB8 DIAG 83240008 00000008 >> PSW = 03EC1000 8180BAD2 >> GPR 0 = 0183F447 01855FB8 3F997F00 3F997FF0 >> GPR 4 = 00000000 0008EE5D 3F9883A0 3F99D078 >> GPR 8 = 3F9888F8 3F988548 BF988F04 3F997E38 >> GPR 12 = 8180BAA0 3F997EA8 97899788 0180BA9E >> >> cp log >> CONNECT= 00:01:02 VIRTCPU= 000:00.05 TOTCPU= 000:00.20 >> LOGOFF AT 14:15:13 EDT THURSDAY 07/02/15 >> >> >> >> >> Le 02/07/2015 14:03, « CMSTSO Pipelines Discussion List on behalf of John >> P. Hartmann » <[email protected] on behalf of >> [email protected]> a écrit : >> >>> Thanks, Alain. >>> >>> Could I trouble you for >>> >>> Note the the length of the command response changes between the two >>> diagnose instructions; on the first one it is effectively x'90e5d', but >>> on the second it is only x'90cfe', the difference being x'14f' or >>> thereabouts. >>> >>> Would you try the failing pipe once more, but without RUN on the trace >>> command and then see what is in storage at address R3 + R5 on the second >>> diagnose instruction? This would be where the missing output is likely >>> to be. >>> >>> >>>> On 07/02/2015 01:53 PM, Alain Benvéniste wrote: >>>> John, >>>> >>>> Valid range are 8000-87BF and 660A-660F >>>> The rest does not exist >>>> >>>> Ready; T=0.02/0.03 13:41:59 >>>> cp trace diag 8 run cmd d psw g >>>> Ready; T=0.01/0.01 13:42:25 >>>> pipe cp q da details 8000-8FFF 660A !> a a a >>>> -> 0180BACE EX 44001000 01855FB8 DIAG 83240008 >>>> 00000008 >>>> PSW = 03EC1000 8180BAD2 >>>> GPR 0 = 0183F447 01855FB8 3F997F00 3F997FF0 >>>> GPR 4 = 00000000 0008EE5D 3F99AAA8 3F99D078 >>>> GPR 8 = 3F9888F8 3F99AC50 BF988F04 3F997E38 >>>> GPR 12 = 8180BAA0 3F997EA8 97899788 0180BA9E >>>> -> 0180BACE EX 44001000 01855FB8 DIAG 83240008 >>>> 00000008 >>>> PSW = 03EC0000 8180BAD2 >>>> GPR 0 = 000121CC 01855FB8 3F997F00 3F8DF1A0 >>>> GPR 4 = 00000028 00090CFE 3F99AAA8 3F99D078 >>>> GPR 8 = 3F9888F8 3F99AC50 BF988F04 3F997E38 >>>> GPR 12 = 8180BAA0 3F997EA8 97899788 0180BA9E >>>> Ready(00040); T=0.01/0.26 13:42:56 >>>> sp cons close >>>> -> 00F1E59C DIAG 83130008 00000008 >>>> >>>> >>>> Ready; T=0.01/0.02 13:46:27 >>>> q 660A-660B >>>> DASD 660A CP SYSTEM 630WV2 140 >>>> DASD 660B XX660B >>>> Ready; T=0.01/0.01 13:46:34 >>>> q 8FF0-8FFF >>>> HCPQDV1003E 8FF0-8FFF was not found. >>>> Ready(01003); T=0.01/0.01 13:47:01 >>>> q 87BF >>>> DASD 87BF XX67BF >>>> Ready; T=0.01/0.01 13:47:11 >>>> >>>> >>>> >>>> >>>> Le 02/07/2015 12:39, « CMS/TSO Pipelines Discussion List on behalf of >>>> John >>>> P. Hartmann » <[email protected] on behalf of >>>> [email protected]> a écrit : >>>> >>>>> Alain, have you got devices 8FFF, 660A and 660B? >>>>> >>>>> Please do >>>>> >>>>> CP TRACE DIAG 8 RUN CMD D PSW G >>>>> >>>>> while running the failing pipeline. >>>>> >>>>>> On 06/30/2015 04:06 PM, Alain Benveniste wrote: >>>>>> Hi, >>>>>> >>>>>> If i do a q da details 8000-8FFF 660A through CP I get the result, >>>>>> with >>>>>> a PIPE CP ...... !> a a a, 660A does not appear in the result, the >>>>>> same >>>>>> with 660A-660A instead. With 660A-660B it works. >>>>>> >>>>>> Regards >>>>>> Alain >>>>>>
