Re-running failed event actions with the Command Line

You can use the Command Line interface to re-run failed events.

This will re-process the actions for all current events of the given criteria, and output the results to a log file.

There is no notification of failed events so regular checks should be made. You might decide to set up regular scheduled re-runs to ensure that failed events do not get missed.

Parameters

Ensure you follow the required conventions when specifying user credentials and subject parameters.

Parameters not specified in the Command Line will not be included in the output. Passing an empty string for any of the parameters in bold below will treat them as “any”.

Column	Description
Username	Current user's MACRO login user name
Password	User's MACRO password
Database	Name of MACRO database
Role	User role for login
Study	Name of study for which failed events are to be re-run
Site	Code of site for which failed events are to be re-run
Subject	Subject Id of the subject for whom events are to be re-run
Eventcode	Unique code of the event to be re-run.
Eventstatus	All failed events with this status will be re-run
Logfilelocation	Location of the log file to which the results will be written

Command Line and result format

/EM/username/password/database/role/study/site/subject/eventCode/eventStatus/logFileLocation

Results are written to a log file in the location specified in the Logfilelocation parameter.

Each processed event action is listed in the log file with the appropriate message:

Event {event details} processed successfully
Processing of event {event details} failed with the following message: {message details}
MACRO cannot process event {event details} as it has an action type of None

If the Command Line format contains errors, such as missing or unexpected parameters, a Command Line error will be written to a log file in the MACRO Temp folder. The error log file name will be of the form: EMCLyyyymmddhhmmss.log indicating the timestamp of the error. If more than one error log is written within a second, the file names will have additional numeric suffixes.

Examples

To re-run the actions for all failed and unprocessed events at site 'london' in study 'DemoStudy40':

InferMed.M40.MACRO_EM.exe/EM/rde/macrotm/M4DB/FullUser/Demostudy40/london////C:\EventsLog.log

To re-run all 'event1' event actions of status '-1' for subject '1' in study 'Demostudy40' at site 'london':

InferMed.M40.MACRO_EM.exe/EM/rde/macrotm/M4DB/FullUser/Demostudy40/london/1/event1/-1/CL\EventsLog.log