Conference iosg::all-in-1_v30

The Printer Table Interface forms in ALL-IN-1 are the same as in
WPS-PLUS/VMS.  The setting of the Print Table field length to 12 characters
was done by the WPS-PLUS group.  It may be for compatability with MS-DOS
which has 12 character file names - 8 for the name, 1 for the '.' and 3 for
the extension. 

ALL-IN-1 allows the device name field in a Printer Type entry to be 30
characters.  The value of this field is passed to the WPS-PLUS formatter as 
the device type parameter.  

I ran a test with the WPS-PLUS V4.1 formatter (in ALL-IN-1 V3.0) and it
accepts device type parameters longer than 8 characters.  Therefore a
customization to allow 28 character characters might work. 

You should ask the same question in the WPS-PLUS conference in case there 
are other reasons for limiting the printer table length.


Richard    

    Thanks for your reply Richard.
    
    WPS-PLUS replied that the reason they were keeping the lengths 
    short was to comply with DOS, and didn't know of any other problem
    associated with this.
    
    However, when I did try this, it hits a problem
     
    934       ! %OA-I-LOGFUN, Function: WPSPLUS_PTU
    934       ! GET Symbol: #PTU_1
    934       !      Value: 2
    934       ! GET Symbol: #PTU_2
    935       !      Value: stev6.pra
    935       ! GET Symbol: #PTU_3
    935       !      Value:
    939       ! %OA-I-LOGFUN, Function: DISPLAY         Cannot open table
    file, inv
    939       ! %OA-I-LOGFUN, Function: FORCE
    939       ! OA$FRM_DISPLAY: Displaying 0036ECF0 PTU_CREATE_TABLE
    ! Cannot open table file, invalid format
    
    
    What does this new hoopy function do and can the customer do anything?
    If we can't fix this, then he can't upgrade to v.4.0.
    
    Thanks
    julia

    
    Julia,
    
    Is the STEV6.PRA a V3.1 printer table? I was under the impression (but
    Richard can correct me) that for use of the WPSPLUS_PTU function (which
    is a front-end to the PTU editor) of WPS-PLUS V4.0 you needed to
    convert (option CO) the table first. What happens if you do that first?
    
    Ciao,
    
    	Simon 

    Simon
    
    No, STEV6 is the new name.  It is using LN03.pra which is v.4 
    format.  If I do allin1/nocustom I can create the new table no
    problem.  If I convert the LN03.PRA table first, I get a SET NOT
    OPEN error.  Doing this /nocustom works fine.
    
    Julia

    Hi,
    
    	I have now taken over this problem, and have some new queries to
    add to it.
    
    	I have found the same problem in that if I extend the fields on the
    PTU_CREATE_TABLE form, and try to create a table from a v4.0 table, I
    get the error
    
    cannot open table file, invalid format
    
    	The strange thing is that I have spoken to the customer this
    morning, and he has managed to get this to work (with the same changes
    applied!!), but he has problems left with the layout of the FO and KY
    options.
    
    	He has moved the Current Table: XXXXXXXXXXX to the left hand side
    of the screen for all the PTU options so that it can be extended, but 
    finds that if he calls FO, for example, he gets
    
    Current Table:                                             JULIE.PRA
    
    at the top of the screen. I have found the same problem even after
    changing the ptu_attribute_menu to change the location of the Current
    Table, so I cannot understand why the printer table name is appearing
    at the wrong place on the scrren, as the TABLE_NAME field is defined
    on the left-hand side.
    
    	After looking at the named data, the only information that is
    passed is
    
    #ptu_1=9
    #ptu_2=1
    wpsplus_ptu
    
    	I cannot find any information on the function WPSPLUS_PTU - does
    anyone have any further info to help me work out what is going wrong?
    
    		Thanks     
    			Julie

The WPSPLUS_PTU function is the ALL-IN-1 Application Programming Interface 
to the WPS-PLUS Printer Table Utility.  This function and its associated 
forms and scripts are written by the WPS-PLUS group.

It would be better to ask detailed questions about WPSPLUS_PTU in the
WPS-PLUS conference.


Richard

    
    Julie,
    
    Before you switch to the WPS-PLUS conference (as Richard correctly
    suggested), the options FO and KY use forms:
    
    	PTU_ATT_FONTS_INDEX
    	PTU_ATT_KEYWORDS_INDEX
    
    Ciao,
    
    	Simon

    Hi,
    
    	As I would not be customising named data using WPSPLUS_PTU in
    WPS-PLUS standalone, I thought this note would be better here, but I
    will repost it into the correct notes conference,
    
    	Thanks                      
    		Julie