Any ideas why the second HOST call does not work???

Question

Hi Folks.
I have written the following code which works fine in all but one respect.
The code creates a zip file on a server (Accessed over a network) hence the full windows network path name.
The call to host on the server works in terms of running the zipinvoices.bat file and the zip file is generated on the server in the correct location.
The prigram unit also generates the correctly formatted mailinvoices.bat file. However, the second call to HOST does not run/execute the mailinvoices.bat file. If I go to the server and run the mailinvoices.bat file directly, it runs perfectly and emails the file to me, no problemo.
Why does the second call to HOST from the client machine not run?
Any clues anyone???
Cheers
Simon Gadd
PROCEDURE send_email_invoices_pu_p (p_organisation IN VARCHAR2) IS
v_processing_cycle          CHAR(4);     
     v_alert_but                              NUMBER;
     v_error_num                              NUMBER;
     v_sent_status                     NUMBER(1);
v_stage                                        NUMBER(1);
v_year                                        VARCHAR2(4);
v_month                                        VARCHAR2(9);
v_folder_name                         VARCHAR2(25); -- Name of the file which holds the 'Printed' invoices in the receivables folder. v_organisation                    VARCHAR2(50);
v_password                              VARCHAR2(25);
v_organisation                    VARCHAR2(25);
     v_host_command                    VARCHAR2(100);
v_from_name                              VARCHAR2(100);
v_to_name                                   VARCHAR2(100);
v_subject                                   VARCHAR2(100);
v_error_txt                              VARCHAR2(200);
v_file                                        VARCHAR2(200);
v_message                                   VARCHAR2(500);
     v_line_buffer                         VARCHAR2(5000);
v_working                                   BOOLEAN := TRUE;
v_zipinvoices_bat               TEXT_IO.FILE_TYPE;
     v_mailinvoices_bat          TEXT_IO.FILE_TYPE;
     CURSOR c_sent_status IS
          SELECT sent
          FROM INVOICE_EMAIL
          WHERE UPPER(ORGANISATION) = UPPER(v_organisation);
     CURSOR c_select_folder IS
          SELECT folder
          FROM INVOICE_EMAIL
          WHERE UPPER(ORGANISATION) = UPPER(v_organisation);     
CURSOR c_select_email_elements IS
SELECT      send_to,
                    send_from
FROM INVOICE_EMAIL
          WHERE UPPER(ORGANISATION) = UPPER(v_organisation);
BEGIN
v_organisation := p_organisation;
-- Check to see if the invoices have already been e-mailed for this Procssing Cycle. If they have,
-- then warn the user of this and get them to confirm that they wish to proceed and e-mail them again.
-- The batch e-mail process will re-zip the invoices (ignoring a pre existing .zip file) and overwrite
-- the existing zip file if it exists or generate it if it does not exist.
     OPEN c_sent_status;
          FETCH c_sent_status INTO v_sent_status;
     CLOSE c_sent_status;     
     IF v_sent_status = 1 THEN
          v_alert_but := SHOW_ALERT('SEND_AGAIN_ALRT');
               IF v_alert_but = ALERT_BUTTON2 THEN RAISE FORM_TRIGGER_FAILURE;
                    ELSE NULL;
               END IF;
     END IF;
:CONTROL.WORKING := 'Started Zipping invoices for '||INITCAP(v_organisation)||'.'||CHR(10)||'Please wait..';
SYNCHRONIZE;
-- The following code opens the zipinvoices.bat file which resides in the root folder \\Ebony\c$\FCSS\DB_SCRIPTS\ and modifies it ready to
-- zip up the invoices in the relevant organisation's invoice folder for the current processing cycle.
v_processing_cycle := GET_CURRENT_TRAFFIC_PERIOD;
v_month := RTRIM(INITCAP(TO_CHAR(TO_DATE(v_processing_cycle, 'MMYY'), 'MONTH')));
v_year := (TO_CHAR(TO_DATE(v_processing_cycle, 'MMYY'), 'YYYY'));
     OPEN c_select_folder;
     FETCH c_select_folder INTO v_folder_name;
     CLOSE c_select_folder;
KILL_OLD_ZIP_PU_P('del \\Ebony\c$\FCSS\CYCLE_DATA\'||v_processing_cycle||'\receivables\'||v_folder_name||'\invoices.zip');
SELECT zip_password
INTO v_password
FROM INVOICE_EMAIL
WHERE UPPER(ORGANISATION) = UPPER(v_organisation);
v_zipinvoices_bat := TEXT_IO.FOPEN('\\Ebony\c$\FCSS\DB_SCRIPTS\zipinvoices.bat', 'w');
v_line_buffer := 'cd..';
TEXT_IO.PUT_LINE (v_zipinvoices_bat, v_line_buffer);
v_line_buffer := 'cd..';
TEXT_IO.PUT_LINE (v_zipinvoices_bat, v_line_buffer);
v_line_buffer := 'wzzip -s'||v_password||' -x*.zip -ybc \\Ebony\c$\FCSS\CYCLE_DATA\'||v_processing_cycle||'\receivables\'||v_folder_name||'\invoices \\Ebony\c$\FCSS\CYCLE_DATA\'||v_processing_cycle||'\receivables\'||v_folder_name||'\*.*';
TEXT_IO.PUT_LINE (v_zipinvoices_bat, v_line_buffer);
v_line_buffer := 'exit';
TEXT_IO.PUT_LINE (v_zipinvoices_bat, v_line_buffer);
TEXT_IO.FCLOSE (v_zipinvoices_bat);
-- The following code executes the freshly edited \\Ebony\c$\FCSS\DB_SCRIPTS\zipinvoices.bat file to produce the zipped invoices file
-- ready to be e-mailed out to the address specified in the INVOICE_EMAIL table for the relevant organisation.
v_host_command := '\\Ebony\c$\FCSS\DB_SCRIPTS\zipinvoices.bat';
v_stage := 1;
HOST (v_host_command, NO_SCREEN);
IF NOT Form_Success THEN
     IF v_stage = 1 THEN
     :CONTROL.WORKING := 'Error -- The .zip file for '||INITCAP(v_organisation)||' was not produced.';
          SYNCHRONIZE;     
     ELSIF v_STAGE = 2 THEN
     :CONTROL.WORKING := 'Error -- The zipped invoices file for '||INITCAP(v_organisation)||' was not emailed.';
          SYNCHRONIZE;               
          END IF;     
ELSE NULL;
END IF;
:CONTROL.WORKING := 'All invoices for '||INITCAP(v_organisation)||' successfully zipped.'||CHR(10)||'Attempting to send via e-mail.'||CHR(10)||'Please wait..';
SYNCHRONIZE;
-- The following code e-mails the freshly created .zip file for the relevant organisation and e-mails it to the
-- recipient specified in the relevant row in the INVOICE_EMAIL programme along with from address, subject and
-- message if specified.
OPEN c_select_email_elements;
FETCH c_select_email_elements INTO
v_to_name,
v_from_name;
CLOSE c_select_email_elements;
v_stage := 2;
v_mailinvoices_bat := TEXT_IO.FOPEN('\\Ebony\c$\FCSS\DB_SCRIPTS\mailinvoices.bat', 'w');
v_line_buffer := 'cd..';
TEXT_IO.PUT_LINE (v_mailinvoices_bat, v_line_buffer);
v_line_buffer := 'cd..';
TEXT_IO.PUT_LINE (v_mailinvoices_bat, v_line_buffer);
v_line_buffer := 'clemail -quiet -smtpserver mailhost.0800dial.com -smtpport 25 -to '||v_to_name||' -from '||v_from_name||' -subject "'||v_month||' '||v_year||' Roaming Traffic Invoices from United Clearing Ltd" -bodyfile \\Ebony\c$\FCSS\DB_SCRIPTS\invoice_body.txt -attach \\Ebony\c$\FCSS\CYCLE_DATA\'||v_processing_cycle||'\receivables\'||v_folder_name||'\invoices.zip';
TEXT_IO.PUT_LINE (v_mailinvoices_bat, v_line_buffer);
v_line_buffer := 'exit';
TEXT_IO.PUT_LINE (v_mailinvoices_bat, v_line_buffer);
TEXT_IO.FCLOSE (v_mailinvoices_bat);
v_host_command := '\\Ebony\c$\FCSS\DB_SCRIPTS\mailinvoices.bat';
HOST (v_host_command, NO_SCREEN);
IF NOT Form_Success THEN
     IF v_stage = 1 THEN
     :CONTROL.WORKING := 'Error -- The .zip file for '||INITCAP(v_organisation)||' was not produced.';
          SYNCHRONIZE;     
     ELSIF v_STAGE = 2 THEN
     :CONTROL.WORKING := 'Error -- The zipped invoices file for '||INITCAP(v_organisation)||' was not emailed.';
          SYNCHRONIZE;               
          END IF;     
ELSE NULL;
END IF;
UPDATE INVOICE_EMAIL
     SET sent = 1
          WHERE UPPER(ORGANISATION) = UPPER(v_organisation);
COMMIT;
GO_BLOCK ('INVOICE_EMAIL');
EXECUTE_QUERY;               
:CONTROL.WORKING := 'Please press a button on the left to e-mail invoices to the organisations listed.';
SYNCHRONIZE;
EXCEPTION
     WHEN OTHERS THEN
          v_error_num := SQLCODE;
          v_error_txt := SUBSTR(SQLERRM, 1, 200);
          MESSAGE('The error was: '||v_error_txt||' and the code was: '||v_error_num);
          RAISE FORM_TRIGGER_FAILURE;
END;

Answer 1

As a suggestion I'd put the Text_io segments into their own begin - exception - end sub-blocks within the main code. This way if Text_io does raise an exception you can catch it earlier as it may be able to recover - That is if it is a text_io exception.
Other than that you;ll have to step through in Debug.