$TXT Created by LAFOND,ROBERT at MNTVBB.FO-WASH.MED.VA.GOV (KIDS) on Monday, 01/30/06 at 08:47 ============================================================================= Run Date: FEB 15, 2006 Designation: PRC*5.1*83 Package : PRC - IFCAP Priority: EMERGENCY Version : 5.1 SEQ #79 Status: Released Compliance Date: FEB 28, 2006 ============================================================================= Associated patches: (v)PRC*5.1*1 <<= must be installed BEFORE `PRC*5.1*83' (v)PRC*5.1*84 <<= must be installed BEFORE `PRC*5.1*83' Subject: Clinical Logistics Report Server (CLRS) - Data Extract and File Transfer Category: - Enhancement () - Routine Description: ============ !!!ATTENTION IRM!!!! The Clinical Logistics Office (CLO) mandates all sites install this patch NO LATER THAN Tuesday, February 28, 2006. !!!ATTENTION IRM!!!! ********************************************************* * SPECIAL NOTE * * * * Please verify that your DUZ(0) value is set to "@" * * before installing this patch or scheduling the * * associated background jobs for this patch. * * * ********************************************************* NOTE: An overview of this patch will be provided on the National IRM Call scheduled for 02/22/06. This patch will enhance the Integrated Funds Distribution, Control Point Activity, Accounting, and Procurement (IFCAP) package to capture Purchase Order (PO) Activity and Generic Inventory Package (GIP) module data so the data can be rolled up at the Veterans Integrated Services Network (VISN) and national levels for analysis by the Prosthetic and Clinical Logistics Office (PCLO). This patch contains routines that use existing FileMan Application Program Interfaces (API) to create delimited flat files from the IFCAP application and the GIP module. The GIP extract is performed on the first day of the month. It extracts data from the first day of the previous month to the last day of the previous month. The results are stored in the FileMan CLRS REPORT STORAGE (#446.7) file. The PO Activity extract is initiated on the 15th day of each month. It extracts data from the first day of the finalized data month two months (previous) to the last calendar day of that month. The transactions are pulled from the PO ACTIVITY (#442) file. Once complete, the extracts are transmitted on the 15th of the month via File Transfer Protocol (FTP) to the Clinical Logistics Report Server (CLRS). The field station (each facility) must have at least 10 Megabytes (MB) of memory in its Operating System (OS) available for the extract. Also, TaskMan and MailMan must be running prior to the initiation of the extract. New Application Coordinator Option and System Parameter Definitions ------------------------------------------------------------------- Added to the IFCAP Application Coordinator menu [PRCHUSER COORDINATOR] will be a new submenu, Clinical Logistics Office menu [PRCPLO CLO MENU], that adds three new options: [PRCHLO CLO PROCUREMENT], manual initiation to extract the PO data [PRCPLO CLO GIP OPTION], manual initiation to extract the GIP data [PRCPLO CLO SYSTEM PARAM], allows modification to the four parameter definitions by IRM staff and is restricted to those who hold the security key, XUPROG. The menu option [PRCPLO CLO SYSTEM PARAM] will allow access to the four new parameter definitions enabling each site to adjust the range of GIP reporting covered by the extracts (coordinated by the PCLO). The parameter definitions are: PRCPLO GREATER THAN RANGE (default setting of 90) PRCPLO INACTIVITY RANGE (default setting of 90) PRCPLO REPORT RANGE (default setting of 180) PRCPLO EXTRACT DIRECTORY (no default setting provided) The post install routine, PRC5183P, will initialize these parameters to their default definitions. Then PRC5183P is automatically deleted. The [PRCPLO CLO SYSTEM PARAM] option will allow IRM to edit these parameters as required by the PCLO. The PRCPLO EXTRACT DIRECTORY parameter identifies the directory at the OS level where the extract files will be stored for transfer. Notifications of process status are distributed to users via the newly added PRCPLO CLRS NOTIFICATIONS mail group and users must be added to this mail group to receive notifications of successful processing or exception cases. Documentation Updates: ---------------------- Sites may retrieve the documentation directly via FTP (using BIN mode). The preferred method is to FTP the files from: download.vista.med.va.gov This transmits the files from the first available FTP server. Sites may also elect to retrieve the documentation directly from the ANONYMOUS.SOFTWARE directory from a specific server as follows: Albany: ftp.fo-albany.med.va.gov Hines: ftp.fo-hines.med.va.gov Salt Lake City: ftp.fo-slc.med.va.gov The following manuals have been updated and are available for download: Filename Document Name ----------------------------------------------------------------------- IFCP5_1APPLICATION_COORD.PDF IFCAP V. 5.1 Application Coordinator User's Guide IFCP5_1TECH_MANUAL.PDF IFCAP V. 5.1 Technical Manual These manuals will be available after release of the patch using the following link: http://www.va.gov/vdl/Financial_Admin.asp?appID=42 This patch addresses the following New Service Request (NSR): ------------------------------------------------------ 20050306 This patch addresses the following NOIS/Remedy Ticket(s): --------------------------------------------------------- There are no NOIS/Remedy tickets associated with this patch. Overview of NOIS/Remedy Ticket(s): ---------------------------------- N/A Components sent with Patch --------------------------- The following is a list of the routines included in this patch. The second line of each of these routines now looks like: ;;5.1;IFCAP;**[Patch List]**; Oct 20, 2000 OLD CHECK^XTSUMBLD results Routine Before Patch After Patch Patch List ------- ------------ ----------- ---------- PRC5183P N/A Deleted 83 PRCHLO N/A 1533969 83 PRCHLO1 N/A 6517643 83 PRCHLO1A N/A 10977287 83 PRCHLO2 N/A 12318889 83 PRCHLO2A N/A 5745217 83 PRCHLO3 N/A 11104555 83 PRCHLO4 N/A 9966901 83 PRCHLO4A N/A 9218167 83 PRCHLO5 N/A 16555006 83 PRCPLO N/A 13120616 83 PRCPLO1 N/A 12477317 83 PRCPLO2 N/A 12438784 83 PRCPLO2A N/A 8569282 83 PRCPLO3 N/A 4069122 83 PRCPLO4 N/A 7286842 83 PRCPRSOH 11859868 11859868 84,83 PRCPUSEL 8686621 8686621 1,83 NEW CHECK^XTSUMBLD results Routine Before Patch After Patch Patch List ------- ------------ ----------- ---------- PRC5183P N/A Deleted 83 PRCHLO N/A 6164457 83 PRCHLO1 N/A 28575897 83 PRCHLO1A N/A 66700839 83 PRCHLO2 N/A 59193374 83 PRCHLO2A N/A 22564489 83 PRCHLO3 N/A 56712862 83 PRCHLO4 N/A 83540702 83 PRCHLO4A N/A 45155553 83 PRCHLO5 N/A 93753886 83 PRCPLO N/A 62666305 83 PRCPLO1 N/A 52725276 83 PRCPLO2 N/A 29302908 83 PRCPLO2A N/A 19078579 83 PRCPLO3 N/A 12210109 83 PRCPLO4 N/A 15950699 83 PRCPRSOH 19184669 20391419 84,83 PRCPUSEL 25814572 26828500 1,83 Total number of routines modified - 2 Total number of new routines - 16 Total number of routines deleted - 1 Total number of routines - 18 The following is a list of files included in this patch: UP SEND DATA DATE SEC. COMES SITE RSLV FILE # NAME DD CODE W/FILE DATA PTS -------------------------------------------------------------------- 446.7 CLRS REPORT STORAGE FILE YES NO NO NO NO Partial DD: subDD:446.7 fld: .01 fld:1 fld:2 The following is a list of options included in this patch: Option Name Type New/Modified ----------- ---- ------------ [PRCHUSER COORDINATOR] menu Modified [PRCHLO CLO PROCUREMENT] run routine New [PRCPLO CLO GIP OPTION] run routine New [PRCPLO CLO MENU] menu New [PRCPLO CLO SYSTEM PARAM] run routine New The following is a list of parameters included in this patch: Parameter Definition -------------------- PRCPLO EXTRACT DIRECTORY SEND TO SITE PRCPLO GREATER THAN RANGE SEND TO SITE PRCPLO INACTIVITY RANGE SEND TO SITE PRCPLO REPORT RANGE SEND TO SITE The following is a list of mail groups included in this patch: Mail Group: ----------- PRCPLO CLRS NOTIFICATIONS SEND TO SITE Test Sites: ----------- Cincinnati VAMC Carl Vinson VAMC (Dublin) Kansas City VAMC Minneapolis VAMC Pre-Installation Overview ------------------------- The Pre Installation Instructions detail how the System Manager is to create the extract directory for the CLRS. The extract directory will temporarily contain the station-level data that will be transferred to the CLRS during the FTP process. Post Installation Overview -------------------------- The Post Installation Instructions specify how to schedule the options installed with PRC*5.1*83, the users that should be added to the new mail group, and gives examples of the extract directory parameter setup and validation of that setup. ***************** PRE INSTALLATION INSTRUCTIONS ***************** INSTRUCTIONS FOR SETTING UP THE EXTRACT DIRECTORY FOR THE CLRS -------------------------------------------------------------- Patch PRC*5.1*83 was created to extract and transmit PO Activity and GIP module data from each station to a centrally located Report Server employed by the PCLO. In order for each station to communicate with the CLRS, it is important to establish an extract directory to transfer station- level data to the CLRS. The following steps MUST be performed by the System Manager, because Administrative privileges (for VMS or MS Windows OSs) are needed in order to perform the tasks required. Perform all steps relevant to your OS prior to installing this patch. 1. Security Keys and Privileges ---------------------------- You will need the following system access or privileges: Massachusetts General Hospital Utility Multi-Programming System (MUMPS) Programmer Virtual Memory System (VMS) or Microsoft (MS) Windows/New Technology (NT) Administrator. 2. Station Number Identification ----------------------------- NOTE: Perform this step for each instance of Cache running on your server(s) (single or multiple instances). You should be at the Programmer prompt: > You will need to obtain the station number from your system. NOTE: When your system was configured, a unique number was assigned to the configuration (single station sites and multi-division facilities). In order to obtain the station number (used to name the directory), type the following two commands at the programmer prompt: > S Y=$$GET1^DIQ(4,$$KSP^XUPARAM("INST")_",",99) [Enter] > W Y [Enter] > 500 NOTE: In this example, the site number returned is 500. The command you entered MUST return a site number (which is set in the variable Y). 3. Extract Directory Setup ----------------------- NOTE: The naming convention for directories is different for each OS. Be sure to follow the instructions for your particular OS. a. Cache / VMS Sites NOTE: The proposed naming convention is a recommendation. A more knowledgeable and experienced System Manager may choose to setup the extract directory using existing drives and definitions. The directory name chosen must have the appropriate READ, WRITE, EXECUTE, and DELETE privileges. 1) Set up a VMS Directory named USER$:[CLRSxxx] where xxx is the station number. In our example, the name of the directory would be: USER$:[CLRS500] (station number obtained in step 2). NOTE: This directory will store approximately 10MB of data each month, but will be purged of existing data when the next monthly extract occurs. 2) The new directory MUST have READ, WRITE, EXECUTE, and DELETE privileges for the currently installed Cache instance. You must have administrator privileges when you perform this task in order to assure the directory is setup/created with the necessary permissions. Following is an example for you to follow to set up the extract directory. NOTE: The owner of the directory should be CACHEMGR. $ CREATE/DIRECTORY DISK$:[CLRSnnn] /own=CACHEMGR /PROTECTION=(S:RWED,O:RWED,G:RWED,W:RWED)/LOG NOTE: Where DISK$=the disk of your choice (e.g. USER$, PQ$, etc. - SYS$ is not recommended) and xxx=the station number. 3) Following is an example of the SPOOL directory which is presently configured on your Cache / VMS system. Also, these commands may be performed in VMS to view the SPOOL directory. NOTE: Confirm that the extract directory has similar protections and permissions $ dir user$:[000000]spool.dir/sec Directory USER$:[000000] SPOOL.DIR;1 [CACHEMGR] (RWED,RWED,RWED,RWED) (IDENTIFIER=*,OPTIONS=DEFAULT,ACCESS=READ+WRITE+EXECUTE+DELETE) NOTE: After the extract directory set up is complete, provide the directory name to the IRM IFCAP Application support person responsible for the installation of this patch. The extract directory name will be entered into the PRCPLO EXTRACT DIRECTORY system parameter during patch installation. b. Cache / MS Windows or NT Sites NOTE: The proposed naming convention is a recommendation. A more knowledgeable and experienced System Manager may choose to setup the extract directory using existing drives and definitions. The directory name chosen must have the appropriate READ, WRITE, EXECUTE, and DELETE privileges. 1) Set up an MS Windows directory named D:\CLRSxxx where xxx is the station number. In our example, the name of the directory would be: D:\CLRS500 (station number obtained in step 2). NOTE: This directory will store approximately 10MB of data each month. But will be purged of existing data when the next monthly extract occurs. 2) The new directory MUST have READ, WRITE, EXECUTE, and DELETE privileges for the currently installed MS Windows instance. You must have administrator privileges when you perform this task in order to assure the directory is setup/created with the necessary permissions. *************************************************************** * SPECIAL INSTRUCTIONS FOR WINDOWS/NT STATIONS * * * * The directory set up in the example is D:\CLRS500. * * You MUST append a backslash ( \ ) to the MS Windows * * directory name when you enter a value in the CLO * * System Parameter, for example: D:\CLRS500\ * * * *************************************************************** ==================INSTALLATION INSTRUCTIONS =================== If installed during the normal workday, it is recommended that the following selection(s) in the OPTION (#19) file, and all of their descendants be disabled to prevent possible conflicts while running the KIDS Install. Other VISTA users will not be affected. IFCAP Application Coordinator Menu [PRCHUSER COORDINATOR] Install Time - less than 30 minutes 1. LOAD TRANSPORT GLOBAL --------------------- Choose the PackMan message containing this patch and invoke the INSTALL/CHECK MESSAGE PackMan option. 2. START UP KIDS ------------- Start up the Kernel Installation and Distribution System Menu [XPD MAIN]: Edits and Distribution ... Utilities ... Installation ... Select Kernel Installation & Distribution System Option: INStallation Load a Distribution Print Transport Global Compare Transport Global to Current System Verify Checksums in Transport Global Install Package(s) Restart Install of Package(s) Unload a Distribution Backup a Transport Global Select Installation Option: 3. Select Installation Option: -------------------------- NOTE: The following are OPTIONAL - (When prompted for the INSTALL NAME, enter PRC*5.1*83): a. Backup a Transport Global - This option will create a backup message of any routines exported with this patch. It will not backup any other changes such as DD's or templates. b. Compare Transport Global to Current System - This option will allow you to view all changes that will be made when this patch is installed. It compares all components of this patch (routines, DD's, templates, etc.). c. Verify Checksums in Transport Global - This option will allow you to ensure the integrity of the routines that are in the transport global. 4. Select Installation Option: Install Package(s) ------------------ **This is the step to start the installation of this KIDS patch: a. Choose the Install Package(s) option to start the patch install. Enter the Coordinator for Mail Group ' PRCPLO CLRS NOTIFICATIONS': NOTE: Answer with the IFCAP Application Coordinator. When prompted 'Want KIDS to Rebuild Menu Trees Upon Completion of Install? YES// ' answer YES b. When prompted 'Want KIDS to INHIBIT LOGONs during the install? YES//' answer NO c. When prompted 'Want to DISABLE Scheduled Options, Menu Options, and Protocols? YES//' answer YES d. When prompted 'Enter options you wish to mark as 'Out Of Order':' Enter the following option: IFCAP Application Coordinator Menu [PRCHUSER COORDINATOR] e. When prompted 'Enter protocols you wish to mark as 'Out Of Order':' press **************** POST-INSTALLATION INSTRUCTIONS **************** ********************************************************* * SPECIAL NOTE * * * * Verify that your DUZ(0) value is set to "@" * * before scheduling the associated background * * jobs for this patch. * * * ********************************************************* 1. Mail Group Notification ----------------------- Notifications of process status are distributed to users via the newly added PRCPLO CLRS NOTIFICATIONS mail group and users must be added to this group to receive notifications of successful processing or exception cases. The following individuals should be added to this newly created mail group: IFCAP IRM support staff, IFCAP Application Coordinators, and Supply Systems Analysts responsible for the transmission of the GIP data to the PCLO. 2. Option Scheduling ----------------- Schedule the options to run via the TaskManager by using the Schedule/Unschedule option, [XUTM SCHEDULE]. The options should be set to run using the following values (time displayed is local): a. [PRCPLO CLO GIP OPTION] should be queued to run on the first day of the month at midnight (12:00am), with a rescheduling frequency of "1M" indicating a monthly job, and a special queuing value of "P" indicating a persistent task. b. [PRCHLO CLO PROCUREMENT] should be queued to run on the 15th day of the month at 7:00pm, with a rescheduling frequency of "1M" indicating a monthly job, and a special queuing value of "P" indicating a persistent task. 3. Extract Directory Parameter Setup --------------------------------- Use the [PRCPLO CLO SYSTEM PARAM] option to set up the PRCPLO EXTRACT DIRECTORY. Be sure to coordinate appropriately with the staff responsible for the extract directory setup from the Pre-Installation Instructions. Remember, the [PRCPLO CLO SYSTEM PARAM] option is only available to those who hold the XUPROG security key. NOTE: In the following example, the PRCPLO EXTRACT DIRECTORY parameter is changed from a blank value to $1$DGA2:[ANONYMOUS.CLRS]. THIS VALUE IS NOT a valid entry for your site. Every station's extract directory will be determined by that station's system administrator. Select OPTION NAME: IFCAP APPLICATION COORDINATOR PRCHUSER COORDINATOR IFCAP Application Coordinator Menu Site Parameters EDI Vendor Edit Establish Common Number Series Add/Edit Supply Personnel Barcode Manager Menu ... Clear FMS Exception File Entries FMS Exception Transaction Report PAT Status Report Repost FMS Exceptions Substation Enter/Edit Reinstate IFCAP Terminated User Clinical Logistics Office Menu ... Let Staff Replace Inventory Quantities Posted Dietetic Cost Report Quarterly Review of Vouchers Unposted Dietetic Cost Report Select IFCAP Application Coordinator Menu Option: CLINICAL Logistics Office Menu CLO GIP Reports (CLRS) CLO Procurement Reports (CLRS) CLO System Parameters (CLRS) Select Clinical Logistics Office Menu Option: CLO SYStem Parameters (CLRS) Stock on Hand Report Range: 180// Stock on Hand Report Greater Than Range: 90// Stock Status Report Inactivity Range: 90// CLRS Extract Directory: //$1$DGA2:[ANONYMOUS.CLRS] CLRS Extract Directory successfully set to $1$DGA2:[ANONYMOUS.CLRS] 4. Extract Directory Parameter Setup Validation -------------------------------------------- Run the CLRS extracts manually to ensure a valid setup. An example of the process follows, including the mail messages for the successful FTP transmission and a failed transmission due to an invalid setup. Select OPTION NAME: IFCAP APPLICATION COORDINATOR PRCHUSER COORDINATOR IFCAP Application Coordinator Menu Site Parameters EDI Vendor Edit Establish Common Number Series Add/Edit Supply Personnel Barcode Manager Menu ... Clear FMS Exception File Entries FMS Exception Transaction Report PAT Status Report Repost FMS Exceptions Substation Enter/Edit Reinstate IFCAP Terminated User Clinical Logistics Office Menu ... Let Staff Replace Inventory Quantities Posted Dietetic Cost Report Quarterly Review of Vouchers Unposted Dietetic Cost Report Select IFCAP Application Coordinator Menu Option: CLINICAL LOGISTICS Office Menu CLO GIP Reports (CLRS) CLO Procurement Reports (CLRS) CLO System Parameters (CLRS) Select Clinical Logistics Office Menu Option: CLO GIP Reports (CLRS) Task # 1189727 entered for the CLO GIP Reports. CLO GIP Reports (CLRS) CLO Procurement Reports (CLRS) CLO System Parameters (CLRS) ************************************************************************ * * * NOTE: Be sure to verify that you have received a MailMan message * * indicating that the CLO GIP Reports completed before executing * * the CLO Procurement Reports. If the CLO GIP Reports have not * * completed you will receive an exception mail message asking * * for you to try the CLO Procurement Reports later. * * * ************************************************************************ Select Clinical Logistics Office Menu Option: CLO PROCUREment Reports (CLRS) Task # 1189729 entered for Procurement Reports. ************************************************************************* * * * NOTE: If the extract directory is invalid, the following message will * * be sent to the PRCPLO CLRS NOTIFICATIONS mail group. * * * ************************************************************************* Subj: CLO Environment Check & Data Transfer for OS / FTP , Dec 07, 200 [#353037] 12/07/05@11:38 17 lines From: CLINICAL LOGISTICS REPORT SERVER In 'IN' basket. Page 1 *New* ------------------------------------------------------------------------- Error with file deletion/cleanup prior to processing. Please contact IRM. This error indicates the CLRS EXTRACT DIRECTORY has not been properly set up during the installation of this patch. (Please refer to the pre installation instructions for PRC*5.1*83) A valid directory must be set up with the proper read/write/execute/delete privileges. In addition, the directory name which you create must be added as the CLRS EXTRACT DIRECTORY through the CLO System Parameters Option. If the field is blank, you will generate this error. Please confirm all steps have been performed according to the pre installation instructions for patch PRC*5.1*83. ************************************************************************* * * * NOTE: If the extract directory is valid and the transfer occurs, the * * following messages will be sent to the PRCPLO CLRS NOTIFICATIONS* * mail group. The directory mentioned in two of these messages is * * pulled dynamically from the PRCPLO EXTRACT DIRECTORY system * * parameter. * * * ************************************************************************* Subj: CLO Environment Check & Data Transfer for OS / FTP , Dec 08, 200 [#353131] 12/08/05@10:28 1 line From: CLINICAL LOGISTICS REPORT SERVER In 'IN' basket. Page 1 *New* ------------------------------------------------------------------------- Built PO Activity Extracts and GIP Extracts for transfer Subj: CLO Environment Check & Data Transfer for OS / FTP , Dec 13, 2005 [#353639] 12/13/05@12:44 23 lines From: CLINICAL LOGISTICS REPORT SERVER In 'IN' basket. Page 1 *New* ------------------------------------------------------------------------- Final FTP Setup complete, beginning FTP Transfer The file transfer to the report server has been initiated. You will be receiving a notification that the FTP process has completed. The notification message should be received within the hour. If you do not receive the FTP process has completed message, please contact IRM. IRM can confirm the process is still running by performing the following command: At the MUMPS Programmer prompt, type D ^%SS See if there are any PRCHLO* routines running. If these routines are present, the process is still running. If you waited one hour, and did not get the FTP process has completed message, a problem was encountered. Further troubleshooting can be performed by examining the LOGFILE CLRSxxxFTP1.LOG where xxx is your station ID#. The logfile is located in the following directory: $1$DGA2:[ANONYMOUS.CLRS] Subj: CLO Environment Check & Data Transfer for OS / FTP , Dec 13, 2005 [#353640] 12/13/05@12:44 125 lines From: CLINICAL LOGISTICS REPORT SERVER In 'IN' basket. Page 1 *New* ------------------------------------------------------------------------- The FTP Transfer process completed, Dec 13, 2005@12:44:51 The Clinical Logistics Office should examine the Report Server FTP directory for your files. If the files from your station are not found, IRM can provide additional troubleshooting steps by examining the LOGFILE CLRSxxxFTP1.LOG where xxx is your station number. The logfile is located in the directory: $1$DGA2:[ANONYMOUS.CLRS] The contents of the logfile are listed below: $ SET VERIFY=(PROCEDURE,IMAGE) $ SET DEFAULT $1$DGA2:[ANONYMOUS.CLRS] $ FTP 10.128.102.204 /INPUT=$1$DGA2:[ANONYMOUS.CLRS]CLRS500FTP.DAT 220 Microsoft FTP Service Connected to vha16dw40.v16.med.va.gov. 331 Password required for clrsadmin. 230 User clrsadmin logged in. Local directory now $1$DGA2:[ANONYMOUS.CLRS] 200 PORT command successful. 150 Opening ASCII mode data connection for ifcp500f1.txt.1. 226 Transfer complete. local: $1$DGA2:[ANONYMOUS.CLRS]IFCP500F1.TXT.1 remote: ifcp500f1.txt.1 37881 bytes sent in 00:00:00.00 seconds (36993.16 Kbytes/s) 200 PORT command successful. 150 Opening ASCII mode data connection for ifcp500f10.txt.1. 226 Transfer complete. local: $1$DGA2:[ANONYMOUS.CLRS]IFCP500F10.TXT.1 remote: ifcp500f10.txt.1 7880 bytes sent in 00:00:00.00 seconds (7695.31 Kbytes/s) 200 PORT command successful. 150 Opening ASCII mode data connection for ifcp500f11.txt.1. 226 Transfer complete. local: $1$DGA2:[ANONYMOUS.CLRS]IFCP500F11.TXT.1 remote: ifcp500f11.txt.1 9724 bytes sent in 00:00:00.00 seconds (9496.09 Kbytes/s) 200 PORT command successful. 150 Opening ASCII mode data connection for ifcp500f12.txt.1. 226 Transfer complete. local: $1$DGA2:[ANONYMOUS.CLRS]IFCP500F12.TXT.1 remote: ifcp500f12.txt.1 ... 200 PORT command successful. 150 Opening ASCII mode data connection for ifcp500g1.txt.1. 226 Transfer complete. local: $1$DGA2:[ANONYMOUS.CLRS]IFCP500G1.TXT.1 remote: ifcp500g1.txt.1 5633 bytes sent in 00:00:00.00 seconds (5500.98 Kbytes/s) 200 PORT command successful. 150 Opening ASCII mode data connection for ifcp500g2.txt.1. 226 Transfer complete. local: $1$DGA2:[ANONYMOUS.CLRS]IFCP500G2.TXT.1 remote: ifcp500g2.txt.1 2731 bytes sent in 00:00:00.00 seconds (2666.99 Kbytes/s) 221 $ EXIT 3 Routine Information: ==================== The checksums below are new checksums, and can be checked with CHECK1^XTSUMBLD. Routine Name: PRC5183P Before: After: B4318344 **83** Description of Changes: New routine. Routine initializes three parameters to their default definitions. Then routine is automatically deleted. Routine Name: PRCHLO Before: After: B6164457 **83** Description of Changes: New Routine This is the master program for PO activity. Routine Name: PRCHLO1 Before: After: B28575897 **83** Description of Changes: New Routine This routine builds the extract for PO data and associated multiples. Routine Name: PRCHLO1A Before: After: B66700839 **83** Description of Changes: New Routine Continues logic and processing for procurement from PRCHLO1. Routine Name: PRCHLO2 Before: After: B59193374 **83** Description of Changes: New Routine Routine builds the extracts for PO item data and associated mutliples. Routine Name: PRCHLO2A Before: After: B22564489 **83** Description of Changes: New Routine Continues logic and processing from PRCHLO2. Routine Name: PRCHLO3 Before: After: B56712862 **83** Description of Changes: New Routine This routine prints out the formatted data PO activity file. Routine Name: PRCHLO4 Before: After: B83540702 **83** Description of Changes: New Routine This routine creates the output files for the procurement extracts. A SACC exemption was granted for the use of $ZF(-1) in this routine. Routine Name: PRCHLO4A Before: After: B45155553 **83** Description of Changes: New Routine Used to build and transfer files to the CLRS for Windows based sites. A SACC exemption was granted for the use of $ZF(-1) in this routine. Routine Name: PRCHLO5 Before: After: B93753886 **83** Description of Changes: New Routine Called from an option to task out procurement extracts. A SACC exemption was granted for the use of $ZF(-1) in this routine. Routine Name: PRCPLO Before: After: B62666305 **83** Description of Changes: New Routine This routine will extract the Days of Stock on Hand report data and store it in file #446.7 to await FTP transfer. Copied from ^PRCPRSOH and modified. Routine Name: PRCPLO1 Before: After: B52725276 **83** Description of Changes: New Routine This routine will provide a GIP reporting utility for CLRS by setting up inventory variables and looping through each station and inventory point. Copied from ^PRCPUSEL and modified. Routine Name: PRCPLO2 Before: After: B29302908 **83** Description of Changes: New Routine This routine is used to extract the Stock Status Report and save it into file #446.7 to await FTP transmission. Copied from routine ^PRCPRSSR and modified. Routine Name: PRCPLO2A Before: After: B19078579 **83** Description of Changes: New Routine Continues processing logic from PRCPLO2. Routine Name: PRCPLO3 Before: After: B12210109 **83** Description of Changes: New Routine This routine will be used to task out the GIP report extracts when called from the scheduled option or the user interactive option. Routine Name: PRCPLO4 Before: After: B15950699 **83** Description of Changes: New Routine Called from an option to allow users to edit the system level parameters as instructed by the CLO. Routine Name: PRCPRSOH Before: B19184669 After: B20391419 **84,83** Description of Changes: Cloned to provide functionality for PRCPLO and added here with a note to that effect. Routine Name: PRCPUSEL Before: B25814572 After: B26828500 **1,83** Description of Changes: This routine is cloned to produce functionality in PRCPLO1 and is edited with a note to that effect here. ============================================================================= User Information: Entered By : LAFOND,ROBERT L Date Entered : MAY 11, 2005 Completed By: BURGESS,PATRICIA Date Completed: FEB 15, 2006 Released By : NELSON,VICKI M Date Released : FEB 15, 2006 ============================================================================= Packman Mail Message: ===================== $END TXT