Is z/XDC available to you?  The authorized version might be able to help you 
out there, but I suspect only Dave Cole could tell you that for sure, and if 
so, how to do it.

Peter

From: IBM Mainframe Assembler List <[email protected]> On Behalf 
Of Dave Clark
Sent: Friday, September 22, 2023 1:55 PM
To: [email protected]
Subject: Re: EXCP CCB Status Code Error


"IBM Mainframe Assembler List" <[email protected]> wrote on

09/22/2023 01:36:12 PM:

> The x'40' is an incorrect-length indication.  If you're using

> format-0 CCWs then the count field is required to be non-zero.  As a

> result, a NOP, which doesn't transfer any data, will always end with

> the CCW count \= 0.  If the ORB does not have the incorrect-length-

> suppression (L) bit set and the CCW does not have the SLI flag set

> then incorrect length will be indicated in the subchannel when CE is

> received.  I don't know if you have control over the setting of the

> L bit in the ORB, but the easiest thing to do is probably set SLI

> (x'20' bit) in the CCW flags.  If you're using format-1 CCWs then

> you can either set SLI in the CCW flags or set the count field to 0.





        Thanks for that.  I am using a format-0 CCW and I have the

following when initializing my CCW (WLR = wrong length record).



* INITIALIZE CCW

         LA    R0,SCRBUF               GET ADDRESS OF BUFFER

         L     R1,BUFLEN               GET MAX LENGTH OF BUFFER

         STM   R0,R1,MYCCW+0           PUT IN CHANNEL COMMAND WORD

         MVI   MYCCW+4,X'20'           SUPPRESS WLR





        But now the x'0C40' status has suddenly gone away after I reviewed

and rearranged my code just to "clean" things up.



        However, now I see that am not getting the desired results out of

my appendage routine -- i.e., the wait is being satisifed too early and my

program is sending a message back to the user that input is required even

before they have a chance to send any input.  When they finally do send

some input, it is accepted and processing continues but this keeps

happening every time it comes to the point in the process where user input

is required.  It is a little difficult to debug an appendage routine when

it runs as an extension of the supervisor.  Suggestions anyone?



Sincerely,



Dave Clark

--

This message and any attachments are intended only for the use of the addressee 
and may contain information that is privileged and confidential. If the reader 
of the message is not the intended recipient or an authorized representative of 
the intended recipient, you are hereby notified that any dissemination of this 
communication is strictly prohibited. If you have received this communication 
in error, please notify us immediately by e-mail and delete the message and any 
attachments from your system.

Reply via email to