Resent-Organization: Stanford Linear Accelerator Center
Resent-Subject: PIPEDEMO Problems
Newsgroups: bit.listserv.cmspip-l
Date:         Thu, 27 Aug 1992 12:41:47 PST
Comments:     Resent-From: Chuck Boeheim <BOEHEIM@SLACVM>
Comments:     Originally-From: Melinda Varian <MAINT@PUCC.BITNET>
From:         Chuck Boeheim <BOEHEIM@SLACVM.BITNET>
Subject:      Re: FULLSCR problems

Despite extensive beta testing on as many different environments
as I could find, there still seems to be two major problems.
Now I know how IBM feels sometimes. (:>)

First, Pipedemo seems to stall on some systems.  I can't reproduce
that problem on my system, and I am working with some people on
other systems to understand the problem.

Second, Pipedemo will fail on some systems with something like this:

PIPIOS292E I/O error on CONSOLE; CSW X'002EC8B0 0E000000', CCW X'29291EF1
2080050C'.
PIPMSG004I ... Issued from stage 8 of pipeline 1 name "RUNPIPE".
PIPMSG001I ... Running "fullscr noclose path pipedemo condread".
PIPIOS293I Sense 01.

This is a bug in pipes itself, the fix for which is described below.
It seems to only happen in XA mode virtual machines, so one bypass
may be to run in 370 mode.  If anyone has applied the fix below and
still sees the problem, please let me know.

Finally, I want you all to know that I appreciate your comments, and
will work to get you a fix as quickly as possible.  However I have
a three day holiday planned for this weekend, so my replies and my
fixes will probably have to wait until early next week.  I hope
that you'll forgive me for the delay. (:>)

-Chuck

------------------------------------------------------------------------
Chuck Boeheim                                  Boeheim@SLAC.Stanford.Edu
Server Computing Group                                    (415) 926-4640

----------------------------Original message----------------------------
The problem that Katherine Faella reported earlier this week when
running Gopher from a 7171-attached device or a TN3270 session in
an XA-mode virtual machine with CMS Pipelines 1.1.6 is in fact a
Pipes problem.  The Piper has generated the following fix for 1.1.6
(and one assumes that there will be an APAR for CMS 8):

:READ  PIPSCR   AUXFIX   Z1 PIPFIX 08/05/92 15:40:08
FOOLPRF  - 216 Fool CONSOLE right.

:READ  PIPSCR   FOOLPRF  Z1 PIPFIX 08/05/92 15:40:19
./ * PIPSCR   FOOLPRF   Created 5 Aug 1992 17:40:08 by JOHN at DKIBMVM2.
./ I 00420000          $ 425000 5000                  08/05/92 17:40:19
*  5 Aug 1992  216 Fool CONSOLE right.                         FOOLPRF
./ R 06580000          $ 6584990 4990                 08/05/92 17:40:19
 LA      R4,CONQRY            Get query response from OPEN     FOOLPRF

You will find detailed instructions for applying a fix to Pipes in the
PRPQ Installation Manual, but I'll summarize the process here:

1.  Make sure that your PIPE CNTRL file references the correct MACLIBs;
    the first record should be:

    TEXT MACS PIPGBL PIPEIF DMSGPI DMSOM OSMACRO OSMACRO1 OSPSI

2.  Make sure you have a PIPEIF MACLIB and a PIPGBL MACLIB (if not,
    generate them according to the instructions in the manual).

3.  Make sure you have the Assembler H disk accessed.

4.  PIPASM PIPSCR, which will create PIPSCR TXTFIX.

5.  PIPGMOD, which will create NXPIPE MODULE.  (You will need to
    specifiy PIPGMOD ARIRVSTC.TEXT, if you use SQL with Pipes; see
    the Installation Manual.)

6.  PIPINIT TEST, which will allow you to test this new module.

7.  When you are happy with the new module,
    RENAME NXPIPE MODULE A PIPELINE MODULE A

8.  Deliver the new module to your public Pipes disk.

Melinda
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU