[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | *OLD* ALL-IN-1 (tm) Support Conference | 
| Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 | 
| Moderator: | IOSG::PYE | 
|  | 
| Created: | Thu Jan 30 1992 | 
| Last Modified: | Tue Jan 23 1996 | 
| Last Successful Update: | Fri Jun 06 1997 | 
| Number of topics: | 4343 | 
| Total number of notes: | 18308 | 
3777.0. "losing blank lines after VTX$QUEUE revisited" by GIDDAY::LEH () Wed Jan 19 1994 02:19
VMS 5.5-2   +  IOS 3.0-1   +   VTX 4.1
Note 2506 described seemingly identical problem but on IOS 2.4 and VTX 5.0 and 
it said the fix was provided by 
ALL-IN-1 patch A1024CSP046 for ALL-IN-1 V2.4 + WPS-PLUS V4.0
ALL-IN-1 patch A1_FIX012030 for ALL-IN V3.0 + WPS-PLUS V4.1
This customer installed A1_FIX012030 but the problem seemed to have remained. 
Care has been given to patch install and postinstal, including the addition of 
the keyword TRAILING_BLANK_LINES into VT200.PRA, VT300.PRA and LN03.PRA.
I seeemed to be able to support customer claims with our inhouse testing.
The bug seemed to be have been caused by VTX$QUEUE formatting of WPL doc where 
main problems were found to date:
o doc with TDE picture upset terminal settings ( see note 3764)
o loss of blank lines : note 2506 and this note 
So here it goes:
The source WPL doc with VTX Workbench header file:
--------------------------------- TOP   -----------------------------------
<NP>
<OUTPUT FILENAME>: hong9
<LINES PER PAGE>: 22
<INCLUDE MORE LINE>: Y
<START MORE LINE TEXT>
                                                            More -->
        <-- Prev                                            More -->
        <-- Prev
<END MORE LINE TEXT>
---
--------------------------------- NEW PAGE -------------------------------------
line 19                      LOGO LINE 1
22                      LOGO LINE 2
31                      LOGO LINE 3
34                       LOGO LINE 4
38                       LOGO LINE 5
61                      DATE: 1-JAN-94
--------------------------------- NEW PAGE -------------------------------------
line 2  >>>     para 1 abc abc
dkldkl;s
dsl;ad
dsal;d
dsadsa
dsal;
line 10 >>>     para 2 djksal dkasl;dkl;dsal ;dsa
dl;sad
dsa'd;sad'
dl;sad
dsal;d
dksal
line 20 >>>     para 3 dklsad
da
sdsa
dsad
line 25 >>>     para 4 dkladklsa
sa
sa
aa
da
dsad
sadsa
dsa
dsad
sad
sad
sadsa
dsa
dsad
sadsadsadsadsadsa
dsad
sadsad
sad
line 45 >>>     no more para on this page
--------------------------------- BOTTOM -----------------------------------
This doc was printed via VTX$QUEUE/ VT200 and page settings as follows:
   Page size (lines):                    66   
   Top margin (lines):                    0   
   Bottom margin (lines):                 0   
giving the following output in VTX$WB_FILES
-------------------------------------------------------------------------------
line 19                      LOGO LINE 1
22                      LOGO LINE 2
31                      LOGO LINE 3
34                       LOGO LINE 4
38                       LOGO LINE 5
                                                            More -->
-------------------------------------------------------------------------------
61                      DATE: 1-JAN-94
line 2  >>>     para 1 abc abc
dkldkl;s
dsl;ad
dsal;d
dsadsa
dsal;
line 10 >>>     para 2 djksal dkasl;dkl;dsal ;dsa
dl;sad
dsa'd;sad'
dl;sad
dsal;d
dksal
        <-- Prev                                            More -->
-------------------------------------------------------------------------------
sad
line 45 >>>     no more para on this page
        <-- Prev                                            More -->
-------------------------------------------------------------------------------
        <-- Prev
-------------------------------------------------------------------------------
Apparently, those blank lines in WPL doc shown with <CR> in WPSPLUS view mode
were ignored by VTX$QUEUE processing, which resulted in spacing problems in 
VTX output files. For instance in the above doc, line 1 thru line 18 were 
blanks , thus making VTX output had the first line on VTX screen being line 
19. However, it seemed if a non-blank character, e.g. space or tilde, were put 
in line 1, then output from VTX$QUEUE processing was OK. This workaround was 
clumpsy since the author had to make sure VTX page, usually starting at line 
22 and multiple thereof, DOESN'T start with a blank line
The following is the output of a workaround
-------------------------------------------------------------------------------
~
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
line 19                      LOGO LINE 1
 
 
line 22                      LOGO LINE 2
                                                            More -->
-------------------------------------------------------------------------------
~
 
*
*
*
*
*
*
31                      LOGO LINE 3
*
*
34                       LOGO LINE 4
*
*
*
38                       LOGO LINE 5
*
*
*
*
*
*
        <-- Prev                                            More -->
-------------------------------------------------------------------------------
line 2  >>>     para 1 abc abc
dkldkl;s
dsl;ad
dsal;d
dsadsa
dsal;
line 10 >>>     para 2 djksal dkasl;dkl;dsal ;dsa
dl;sad
dsa'd;sad'
dl;sad
dsal;d
dksal
line 20 >>>     para 3 dklsad
da
sdsa
dsad
        <-- Prev                                            More -->
-------------------------------------------------------------------------------
line 25 >>>     para 4 dkladklsa
sa
sa
aa
da
dsad
sadsa
dsa
dsad
sad
sad
sadsa
dsa
dsad
sadsadsadsadsadsa
dsad
sadsad
sad
line 45 >>>     no more para on this page
line 25 >>>     para 4 dkladklsa
sa
sa
aa
da
dsad
sadsa
dsa
dsad
sad
sad
sadsa
dsa
dsad
sadsadsadsadsadsa
dsad
sadsad
sad
line 45 >>>     no more para on this page
        <-- Prev                                            More -->
-------------------------------------------------------------------------------
        <-- Prev
-------------------------------------------------------------------------------
Can someone try out on a IOS 3.0 system with patch A1_FIX012030 installed; 
also I don't believe VTX itself played any part. Version 4.1 is installed in 
this case, so it is probably not worth upgrading it to 5.%
Hong
CSC Sydney
| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 3777.1 | don't think ICF #6 would fix it | GIDDAY::LEH |  | Wed Jan 19 1994 10:38 | 8 | 
|  |     An off-line comment suspected ICF #6 might do some good, in addition to
    the already installed ICF #12. Looking at IOSG's patch chart, ICF #6
    summary mentioned only LCI fixes, not VTX problems, which were explicitly
    mentioned in ICF #12 release notes.
    
    Is this correct ?
    
    Hong
 | 
| 3777.2 | Asked Martin? | AIMTEC::WICKS_A | Atlanta's Most (In)famous Welshman | Wed Jan 19 1994 15:44 | 8 | 
|  |     hong,
    
    have you asked IOSG directly, trying to decipher the patch chart is
    enough to give anyone a headache.
    
    regards,
    
    Andrew.D.Wicks
 | 
| 3777.3 | escalated via IPMT | GIDDAY::LEH |  | Thu Jan 20 1994 00:37 | 1 | 
|  |     
 | 
| 3777.4 | solved | BIGTOY::LE | Hong Le, CSC Sydney | Mon Mar 07 1994 01:41 | 2 | 
|  |     Solved with upgrade to VTX 5.* in conjunction with VTX printer tables
    supplied by WPS-PLUS engineering
 |