Skip to main content

Components

Common Characteristics​

All of the LSAM components have the following characteristics:

  • The processes read the LSAM configuration file to initialize system parameters.
  • The processes run as daemon processes with root authority.
  • The processes should always be started from within the LSAM Control Script with the start argument. For information on LSAM commands, refer to UNIX LSAM Commands.
  • All output bound for the terminal is redirected to file "LSAM_output_<SAM_socket>" in the LSAM root directory.

The table below lists the continuous processes of the LSAM with a short description of each component. Click on the link for a more in-depth discussion of the component.

LSAM Continuous Processes

ProcessRequiredShort Description
sma_lsamYesThis process submits jobs to the operating system as instructed by the SAM and monitors the jobs' progress
sma_dispYesThis process manages all communication between the LSAM and the SAM
sma_logYesThis process provides continuous and dependable logging for the LSAM
sma_fadNoThis process(es) is a mechanism allowing the LSAM to trigger events based on the satisfaction of file dependencies - SAM then processes these events
sma_fileinNoThis process allows events to be submitted to the SAM from the LSAM machine
sma_cronmonNoThis process provides a mechanism to allow the LSAM to trigger events for processing by SAM based on cron-activated processes
sma_JORSNoThis process enables the user to view UNIX LSAM job output from the Enterprise Manager, and acts as FTServer during execution of SMA File Transfer (FT) jobs
sma_RMNoThis process is the mechanism by which disk, process, and user-defined resources are monitored and events triggered based upon the state of these resources. SAM then processes these events

sma_lsam​

The sma_lsam submits jobs to the operating system as instructed by the SAM and monitors the jobs' progress. For normal job processing, the LSAM resolves process status requests by searching the job's tracking file, "<LSAM root path>/tracking/<SMA_LSAM_INSTANCE>/<Job_ID>". If the file is not found, the LSAM reports the job as Failed to the SAM.

The sma_lsam process works in the following way:

  1. If a start request is received from the SAM, a child process (also called sma_lsam) is spawned to monitor the job.
  2. After spawning the job, the monitor process sends a message to the parent sma_lsam containing start information. The monitor process then sleeps until the job terminates.
  3. When the job completes, the UNIX operating system wakes the monitor process. Before exiting, the monitor process sends a message to the parent sma_lsam containing completion information.

Characteristics​

The sma_lsam rereads the LSAM configuration parameter max_number_of_jobs_to_run from the configuration file when the LSAM Control Script is executed with the refresh argument. For information on the LSAM Control Script, refer to Updating the LSAM Control Script.

sma_disp​

The message dispatcher (sma_disp) is responsible for communication with the sma_lsam process and with SMANetCom. Communication with SMANetCom is sent on the SAM Socket Number specified in the LSAM Control Script.

Characteristics​

Uses the SAM_SOCKET variable in the LSAM Control Script to communicate with SMANetCom.

Note

If the LSAM receives no communication on a socket after the time specified by the msg_timeout_in_seconds parameter, the LSAM considers the socket inactive and closes it.

Requires the logging system (sma_log) to be active.

sma_log​

The sma_log process provides continuous and dependable logging of the LSAM.

Characteristics​

  • Logs messages containing a date/time-stamp, the machine name, and the process ID (pid) number.
  • By default, writes all informational messages to the <LSAM root path>/log/<SMA_LSAM_INSTANCE>/logfile. The SMA_LOG_DIRECTORY variable contains this directory.
  • By default, writes all error messages to the: <LSAM root path>/log/<SMA_LSAM_INSTANCE>/errfile. The SMA_LOG_DIRECTORY variable contains this directory.
  • If the size of the logfile or errfile reaches the log_file_rollover_size (read from the configuration file), the sma_log renames the file to a unique name and creates a new file.

sma_fad​

The sma_fad process enables the LSAM to send external events to the SAM when certain files meet defined criteria. Additionally, sma_fad offers more features and a dramatic increase in event throughput. For a list of valid OpCon Events, refer to Introduction in the OpCon Events online help. For more information on the SMA File Activity Detection Daemon, refer to SMA File Activity Detection Daemon.

Characteristics​

This process is optional. For information on Deactivating LSAM Components, refer to Deactivating LSAM Components. It reads all of the file dependency criteria and events from a Control File:

LSAM_ROOT/fad/<SMA_LSAM_INSTANCE>/control/<Control file>

The sma_disp process sends the event(s) to the SAM when files meet defined criteria.

sma_filein​

The sma_filein process monitors a MSGIN directory for files containing valid OpCon events to be sent to the SAM. The location of the directory is <LSAM root path>/MSGIN/<SMA_LSAM_INSTANCE> on the machine where the UNIX LSAM resides. Any external program/application may generate and place an ASCII file in this directory. For the SAM to process the event, these ASCII files must contain a properly formatted OpCon event with a User Login ID and event password. For a list of valid OpCon Events, refer to Introduction in the OpCon Events online help.

Note

An event file can only contain one event. Place the event in the first line of the ASCII file.

The sma_filein process watches the MSGIN directory for any text file. Following detection, the process reads the file, passes the text to the SAM for processing, and finally deletes the text file. If the SAM receives an invalid event, the SAM documents the error in the SAM Critical log file.

Characteristics​

  • The sma_filein process is optional. For information on Deactivating LSAM Components, refer to Deactivating LSAM Components.
  • Reads the sma_filein_sleep_time from the configuration file to determine the time to wait between file checks.
  • Processes and deletes all files in the MSGIN directory.
  • After sma_filein reads the file, the sma_disp process sends the event to the SAM.

sma_cronmon​

The sma_cronmon process enables the LSAM to send external events to the SAM based on cron-activated processes. This process searches the cron log for a user-defined string and then sends a user-defined event to SAM.

The cronmon.conf file contains all cron search strings and events. When editing the cronmon.conf file, use the following syntax:

<regular expression search string>#e#<event string>

Characteristics The sma_cronmon process is optional. For information on Deactivating LSAM Components, refer to Deactivating LSAM Components. Reads all of the process dependency criteria from the cronmon.conf file: <LSAM root path>/config/<SMA_LSAM_INSTANCE>/cronmon.conf Searches for the <regular expression search string> in the following possible locations for the cron log: /var/log/cron, /var/cron/log, and /var/adm/cron/log.

When the search string is found, the sma_disp process sends the event to the SAM. For a list of valid OpCon Events, refer to Introduction in the OpCon Events online help.

Example

The following example shows a cronmon.conf file:


/dev/null#e#$THRESHOLD:SET,thresholdnull,1

jobtest#e#$THRESHOLD:SET,findtest,3

sma_JORS​

The sma_JORS (Job Output Retrieval System) process allows the user to view UNIX LSAM job output from the Enterprise Manager, and acts as FTServer during execution of SMA File Transfer (SMAFT) jobs.

Characteristics​

  • Regarding job output, the only available output files are for the last execution.
  • If the UNIX LSAM is not configured with STDOUT and/or STDERR capture turned on, no job output is available for users to view; consequently, users receive a message indicating the absence of STDOUT and STDERR files when attempting to view job output in the Enterprise Manager. For more information on LSAM STDOUT and STDERR redirection setting, refer to JORS and SMAFT Parameters.
  • The socket number specified in the configuration file must match both the JORS Port Number and the File Transfer Port Number specified in the Enterprise Manager.
Configure the JORS and File Transfer Ports in the Enterprise Manager​

For the Enterprise Manager to connect to the LSAM for job output and/or File Transfer, configure the JORS and File Transfer Port Numbers to match the JORS_FT Socket configured through the LSAM.

Note

By default, the LSAM sets the JORS_FT Socket number to the sum of ten plus the LSAM's socket number.

  1. Use menu path: Start > Programs > OpConxps > Enterprise Manager. The OpCon Login screen displays.
  2. In the Username text box, enter a case-sensitive User Login ID (e.g., ocadm).
  3. In the Password text box, enter the case-sensitive password for the user.
  4. In the Profile drop-down list, select the Profile.
  5. Click the Login button to log in to the Enterprise Manager.
  6. Double-click on Machines. The Machines screen displays.
  7. In the Select Machine list, select the UNIX Machine.
  8. Click on Open Advanced Settings Panel. The Advanced Machine Properties window displays.
  9. Click on the Communication Settings tab.
  10. Click the JORS Port Number parameter.
  11. Enter the same value entered for the JORS Socket in the LSAM Configuration in the Modify Parameter frame at the bottom of the screen. For information on the JORS Socket in the LSAM Configuration, refer to JORS_FT socket number.
caution

For JORS and a File Transfer job to function properly, ensure that any firewall on the UNIX machine allows the JORS Port Number (and the matching File Transfer Port Number below) to be open.

  1. Click the Update button.
  2. Click on the File Transfer Settings tab in the Advanced Properties window.
  3. Click on File Transfer parameter.
  4. Select the desired operating mode (None, Send Only, Receive Only, or Two-way) from the drop-down list in the frame below the Advanced Machine Properties.
  5. Click the Update button.
  6. Click on File Transfer IP Address parameter in the File Transfer Settings tab.
  • Enter the machine's IP address.
  • Click the Update button.
  1. Click on File Transfer Port Number parameter in the File Transfer Settings tab.
  • Enter the same value entered for JORS Port Number in step 10-a.
  • Click the Update button.
  1. Click the Save button to save and close the Advanced Settings Panel.
  2. (Optional) Start communication with the machine by:
  • Right-clicking over the graphic to enable the menu in the Communication Status frame.
  • Selecting Start Communication from the menu.
  1. Click on the x to the right of the Machines tab to close the Machines screen.
View Job Output in the Enterprise Manager​
  1. Under the Operation topic, double-click on List.
  2. Click the arrow to expand the specific date.
  3. Click the arrow to expand the specific schedule.
  4. Right-click on the desired job.
  5. Click on View Job Output from the menu. The Job Output Retriever window displays.
  6. Double-click on the Output File(s) name to retrieve the output file information. The Log Viewer window displays.
  7. (Optional) Click the Copy To Clipboard button.
  8. (Optional) Click the Open external editor button to open the file in an external editor (e.g., Notepad).
  9. Click the Close button to close the "Log Viewer" window.
  10. Click the Close button to close the "Job Output Retriever" window.

sma_RN​

The sma_RM process enables the LSAM to send external events to the SAM when certain resource-related criteria are met. For a list of valid OpCon Events, refer to Introduction in the OpCon Events online help. For more information on the SMA Resource Monitor, refer to SMA Resource Monitor (SMA_RM).

Note

The SMA Resource Monitor is a beta program.

Characteristics​

This process is optional. For information on Deactivating LSAM Components, refer to Deactivating LSAM Components. It reads all of the file dependency criteria and events from its Control File:

LSAM_ROOT/config/<SMA_LSAM_INSTANCE>/SMA_RM.conf

The sma_disp process sends the event(s) to the SAM when the resource-related criteria defined within the Control File are met.