"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
--
int.ext: 91078
direct: (937) 531-6378
home: (937) 751-3300
Winsupply Group Services
3110 Kettering Boulevard
Dayton, Ohio 45439 USA
(937) 294-5331
*********************************************************************************************
This email message and any attachments is for use only by the named
addressee(s) and may contain confidential, privileged and/or proprietary
information. If you have received this message in error, please
immediately notify the sender and delete and destroy the message and all
copies. All unauthorized direct or indirect use or disclosure of this
message is strictly prohibited. No right to confidentiality or privilege
is waived or lost by any error in transmission.
*********************************************************************************************
