[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

380.0. "SVC function in DT menu of version 2.3" by VFOVAX::TRAUTWEIN () Tue Mar 31 1992 19:46

    There is a problem with the SVC functionality from the DT menu in 
    ALL-IN-1 version 2.3. When trying to save a binary document without
    conversion to a VMS file the VMS file only gets a single ascii string
    in it that states "Text line unsupported by terminal type." However,
    dumping the file that ALL-IN-1 has the actual document in reveals the
    binary data is in the document. I obtained the file and directory that
    ALL-IN-1 is using by using the FULLDB command. The DSAB is foreign. 
    The type is DOCUMENT. 
    
    This same functionality works in ALL-IN-1 2.4. Also the Atlanta hotline
    has a machine with ALL-IN-1 2.3 in which they repeated the test and it 
    worked for them. They stated that their machine probably has all the 
    patches for version 2.3. Looking in notes there were apparently a
    series of patches for version 2.3. These are 501 to 536. Can anyone
    confirm that one of the patches fixed this particular problem. If so,
    we need to obtain the patch that corrects this problem. 
    
    Upgrading to version 2.4 is not a solution. This functionality was
    promissed to customers to work with version 2.3 without upgrade. 
    If a patch is not the solution, what else is configurable that may 
    provide the solution? The customer experiencing problems at present
    says that they have not customized the document transfer menu. Is there
    something that they must customize for SVC to work?
    
    Thank You in advance for the help,
    
    Ralph

T.R	Title	User	Personal Name	Date	Lines
380.1	It's hard to remember that far back	HYPERS::VICKERS	If it helps a customer, DO IT	`Tue Mar 31 1992 21:22`	17
	I would assume that there are good business reasons for the customer to remain on ALL-IN-1 V2.3 rather than moving to software which provides the improved operations. It most certainly sounds as if the SVC option is doing a convert on the customer's system. You might want to have them do a trace of the SCRIPT and SYMBOL activities when they do a SVC. I don't believe that V2.3 had the /FILE qualifier on the COPY function so I am not sure how the conversion was avoided in V2.3. One approach would be to use the DCL copy command to make the copy. You could customize the SVC code to do so if you must. I am sure that others will be able to give better answers. Hang in there, don
380.2	Don't need DCL in V2.3 - but takes two or more steps	SHALOT::WARFORD	Richard Warford @OPA DTN 393-7495	`Wed Apr 01 1992 03:56`	5
	Instead of using the DCL copy, you could do an ALL-IN-1 COPY function making sure the extensions remained the same, then do a RENAME function. Same result, but no DCL subprocess required. Rick
380.3	Could you supply me the steps to take?	VFOVAX::TRAUTWEIN		`Wed Apr 01 1992 16:23`	9
	I have not had the pleasure of customizing a command such as SVC before. Can you give me the cookbook list of steps I would take to customize SVC so that when that command is invoked it does the ALL-IN-1 copy and rename as you described. Thank you, Ralph
380.4	Nine steps to a better life (or script)	HYPERS::VICKERS	If it helps a customer, DO IT	`Thu Apr 02 1992 07:19`	38
	In doing some research on a V2.4 system I see that the SVC option there uses the DCL COPY to make the copy. I am guessing that this MAY be the case in V2.3 as well. You may wish to examine the OA$DO:DXSV.SCP script to see. Take a look at the code after step 6 below and see what happens right after the SVC_COPY option. You might also wish to try the SVC option with SCRIPT and SYMBOL tracing set to the log file. Take a look at that and see what is going on. 1. Go to the CM menu and use the ADE option to Access the Base Elements. 2. Use the SEL option to select the DXSV script by placing that in the Name field and DO in the Type field. Mash RETURN. 3. Use CO to copy it to the development area. 4. EXIT back to the CM menu. 5. Use E to edit it. 6. Find the label called SVC_COPY and add the code between the !!'s below: (Note that the first !! comments out the existing V2.4 code) .LABEL SVC_COPY !! GET OA$DCL = "COPY " #DX_SRC " " #VMSFILE GET #TMP_FILE = OA$DIR:".;".DEV[#VMSFILE] - OA$DIR:".;".DIR[#VMSFILE] - "TMP_FILE" OA$DIR:".;".TYPE[#DX_SRC] COPY #DX_SRC #TMP_FILE RENAME #TMP_FILE #VMSFILE !! GET #DX_STS = OA$STATUS .GOTO SVC_EXIT 7. Test that the new script works by using the MS DVF option. 8. Once you are happy with it then use the MLA option to move it live. 9. You will then have to use the SM M CSZ PME ML CCM options (with the proper pauses in between) to make the sucker live. Hope this helps, don
380.5	COPY/FILE is new for V3.0	IOSG::MARCHANT	Only parrots succeed	`Sun Apr 05 1992 21:15`	8
	Yes, the `/FILE' qualifier on the COPY command (and APPEND too) is new for V3.0. Both V2.3 & V2.4 (& earlier? - before my time!) use a DCL copy for the SVC option. Cheers, Paul.