1 / 8

work

CLINCAPTURE. SAS. The odm folder is accessed over NFS If odm folder is not available (SAS server is down), extract job is queued.

shania
Download Presentation

work

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CLINCAPTURE SAS • The odm folder is accessed over NFS • If odm folder is not available (SAS server is down), extract job is queued. • When CC restarts, it looks in odm to check the status of sas.zip, odm.zip and manifest.txt in the datset_user_timestamp folders. Performs recovery as needed. • The odm and work folders are local to SAS work odm odm NFS • ClinCapture recovery action at startup time: • -Look dataset_user_timestamp folders in odm. For each folder: • If odm.zip or manifest.txt are not present, recreate the odm.zip + manifest • If sas.zip is present, save it and complete the extract process then delete the folder.

  2. CLINCAPTURE SAS • If odm is available, CC creates the dataset_user_timestamp folder • SAS detects new folder • It waits for the odm.zip + manifest.txt work odm odm Dataset_user_06Feb201418:05:24:20 NFS

  3. CLINCAPTURE SAS • CC adds the odm.zip then the manifest.txt to the dataset_user_timestamp folder. • SAS detects the odm.zip and the manifest.txt files work odm odm Dataset_user_06Feb201418:05:24:20 odm.zip manifest.txt NFS • Note: • I am using ‘odm.zi’p as a short hand for file names like odm1.3_full123_2014-01-29-232853005.xml.zip

  4. CLINCAPTURE SAS • New manifest.txt is found. SAS renames the folder into work • In case of failure/reboot, SAS looks into work to see what recovery is needed. • Note if SAS is down, the odm folder is not available to CC. SAS xtracts will have to be queued. work odm odm Dataset_user_06Feb201418:05:24:20 odm.zip manifest.txt NFS • SAS recovery action at startup time: • -Look for dataset_user_timestamp folders in work. For each folder: • If sas.zip is present with updated manifest.txt, rename the folder into odm. • If sas,zip is not present, generate the sas.zip and update the manifest.txt • If the manifest.txt is not updated, regenerate the sas.zip + update maniftest.txt

  5. CLINCAPTURE SAS • SAS adds the sas.zip then updates the manifest.txt files work Dataset_user_06Feb201418:05:24:20 odm.zip manistest.txt sas.zip odm odm NFS • Note: • I am using ‘’sas.zip’as a short hand for file names like sas_2014-01-29-232853005.xprt.zip

  6. CLINCAPTURE SAS • SAS renames • Dataset_user_timestamp folder into odm work Dataset_user_06Feb201418:05:24:20 odm.zip manifest.txt sas.zip odm odm NFS

  7. CLINCAPTURE SAS • CC detects the sas.zip and updated manifest.txt work odm odm Dataset_user_06Feb201418:05:24:20 odm.zip manifest.zip NFS sas.zip

  8. CLINCAPTURE SAS • CC saves sas.zip work • CC deletes dataset_user_timestamp folder odm odm Dataset_user_06Feb201418:05:24:20 odm.zip manifest.txt NFS sas.zip

More Related