Error Handling in Reflection File Transfer from QUICK

[Marcinik, Roger]

The technique below from Cognos Supportlink works fine as long as the user does
everything properly.  What we are finding in testing is that everything does not
always go right with respect to having the correct file on a good disk in the A:
drive.  Yet pclink starts executing and then the terminal hangs when no file
name is identified.  We are having problems capturing the error or completion
codes from Reflection and then passing this to QUICK to prevent execution of
pclink and to display an error message to user.

Has anyone else experienced this?  Do you have a template that works to prevent
pclink execution when trouble occurs?

We are using PowerHouse  8.19.C4 on an HP3000/987 and Relection 7.00.228 P10.

;============
Invoking Reflection File Transfer from QUICK
By Steve Donoghue, Applications Support Team Leader, Customer Support, Cognos
Incorporated, Ottawa, Ontario 

The following technique illustrates how to start the Reflection File Transfer
process from within a QUICK screen in an HP/3000 environment. This is a basic
example and is intended to be a starting point for programmers wishing to
implement this functionality in their PowerHouse applications. If, for any
reason, you are required to make modifications to the program in regards to the
Reflection escape sequences, it is recommended you refer to the Reflection
Command Language Manual and the Reflection Technical Reference Manual for more
details. 

This technique was created in the following environment: Reflection 5.10 running
PCLINK5.PUB.SYS on an HP/3000 system. The PowerHouse software version was
8.19C4. 

SCREEN transqkc MENU                                                  

TEMP twenty-seven INTEGER SIGNED SIZE 2    &
         INITIAL 27 RESET AT STARTUP

TEMP escape    CHARACTER SIZE 1    &
         INITIAL CHAR(twenty-seven)[2:1] RESET AT STARTUP

;  See the 'SEND' syntax below. It allows for transfers in either
;  direction i.e. PC-to-Host or Host-to-PC

;  The &oF portion of the escape sequence below tells Reflection 
;  to never return the completion code. This means we do not need
;  to code an ACCEPT verb to capture the completion code.

TEMP tran_comm CHARACTER SIZE 30  &
         INITIAL 'ECHO ' + escape + '&oFsend {} to {}' RESET AT STARTUP

SKIP TO 5

TITLE '01 Test File Transfer'

PROCEDURE DESIGNER 01
BEGIN
   RUN COMMAND 'setvar hptypeahead false'
   RUN COMMAND tran_comm
   RUN COMMAND "run pclink5.pub.sys"

   ;  The INPUT A;WAIT=1 is needed to capture data returned from PCLINK.
   ;  The 1-second delay is the lowest we can go. Also,
   ;  without this, users will need to press return to get back to the
   ;  action field, which is not desirable.

   RUN COMMAND 'input A;wait=1' NOWARN
   RUN COMMAND 'setvar hptypeahead true'
END

BUILD

= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
This list is closed, thus to post to the list, you must be a subscriber.