[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

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

3685.0. "Merge using a WPS-PLUS template problems" by SNOFS1::SETHI (Sunil Sethi) Tue Dec 21 1993 03:00

    Hi All,
    
    A customer has version 3.0 installed unpatched and is having a problem
    with the merge function.  Looking at page 434 of the Applications
    Reference Volume 2, namely the last paragraph that mentions .BLP for
    ASCII templates and .BLPW for WPS-PLUS templates.
    
    I am rather confused by what is happening at the customer site, so here
    is an outline of the problem.  The template and the output file are 
    WPS-PLUS files and the list file is an ASCII file.  When the customer
    does the following the results are:
    
    1. Merge template.BLPW,outfile.WPL,listfile.lis
    
    	Then does a document transfer to OpenVMS via the SVC, A user than
    	RVC's the file.  The result is a corrupted file.
    
    2. Merge template.WPL,outfile.WPL,listfile.lis
    
        Then does a document transfer to OpenVMS via the SVC, A user than
        RVC's the file.  The result is no corruption of the document.
    
    Can someone clarify what the document is ment to be saying please !!!!
    
    Thanks,
    
    Sunil
T.RTitleUserPersonal
Name		DateLines
3685.1GIDDAY::JOYCEOkay, who moved the goalposts?Wed Jan 05 1994 00:3512
    Sunil,
    
    The doco (APR Vol 2, page 434) is WRONG!!!!!!
    
    The extension for a WPS-PLUS boilerplate is .WPL NOT (as stated in
    the doco) .BLPW.  The CM element type *is* BLPW however and if your
    customer creates their WPS-PLUS boilerplates using CM (as all good
    girls and boys should) and using this element type then the resulting 
    file will have a .WPL extension as required.
    
    Andy
3685.2GIDDAY::SETHIOh what a feeling .....Wed Jan 05 1994 00:4420
    Hi Andy and ALL-IN-1'er,
    
    I have managed to convince the customer that the documentation is
    incorrect.  The line that reads
    
    "By default templates have the file extension .BLP for ASCII templates,
    and .BLPW for WPS-PLUS templates."
    
    Should read 
    
    By default templates have the file extension .BLP for ASCII templates,
    and .WPL for WPS-PLUS templates.
    
    The customer did not use CM to create the template, if they had done so
    entering BLPW as an element type would have created a template with the
    extension of .WPL.  The documentation should be amended.
    
    Thanks,
    
    Sunil
3685.3GIDDAY::JOYCEOkay, who moved the goalposts?Wed Jan 05 1994 04:1212
    
    re .-1
    
  >  Should read 
  >  
  >  By default templates have the file extension .BLP for ASCII templates,
  >  and .WPL for WPS-PLUS templates.
    
    I disagree with the "by default" bit... if a WPS-PLUS boilerplate does
    NOT have a .WPL extension it don't work!