The SunSystems 4.x Macro job step type is used to create a macro file of custom commands and execute it using the SunSystems application provided as a part of Infor SunSystems 4.x. 

 

This job step type extends basic job step functionality.  For details common to all job step types click here.

 

In addition to the common attributes shared by all job steps this job step type has the following attributes:

 

Macro tab:

•Location of Sun Executable: The full path to the SunSystems application executable.  SUN32.EXE for version 4.2.6 and earlier.  SunSystems.V4.Exe for 4.3 and later.  However, on version 4.4 and higher when errors are encountered using the SunSystems.V4.Exe try running under SUN32.EXE to see if the errors resolve themselves.  This is often the case for macros that perform backups and restores.

•Macro Name: The name of the macro to create.  Limited to 8 alphanumeric characters.

•Macro Code: The contents of the SunSystems macro file.  You may use any available parsing token or macro function expression in designing this code.  Consult the SunSystems documentation for specifics of recording and using FreeFormat macros.

Security tab:

•User Name: (Optional) Windows user name in DOMAIN\USERNAME or USERNAME@DOMAIN format.  If provided SunSystems will be launched in the provided security context within its own Window Station Desktop instead of that of the service account when executed automatically or the interactive user when the job is executed manually.  When not provided the process will be launched using the credentials of the pasUnity Processor Agent service.

•Password: (Optional) Password for the Windows user name used to launch the SunSystems process.

Advanced tab:

•Job Timeout: The process timeout.  If this timeout period is exceeded the process is automatically terminated and the job step will report failure.  The default time is 5 minutes.

•Fail Job on Non-Zero Exit Code: If checked the job step will automatically report failure if an exit code with a non-zero value is returned.  SunSystems frequently returns non-zero exit codes depending on the execution environment you are running in so ensure that you need this option before checking it.

•Enable SunSystems Logging: This option is supported on version 4.4 and higher and will produce a log file in the SunSystems installation folder to use in troubleshooting the job.

•Echo Command to the Log: This option, when enabled, will copy the contents of the macro command, working directory, application command line, and any command line arguments to the job log.

After making changes be sure to press the Update button to save your changes.

This is a custom job type that executes an external application in a new thread.  For security details common to all job step types that perform this type of action click here.

When designing SunSystems macros use the letters Y and N on lines by themselves to indicate Yes and No responses to dialog boxes and the characters <> to denote the pressing of the Enter key.

 

When using Windows Integrated security, the first three lines of your macro (which correspond to user name, password, and logon date) should look exactly like this under SunSystems 4.4 and higher:

 

*

*

<>

 

When not using Windows Integrated security, the first three lines of your macro (which correspond to user name, password, and logon date) should look similar to this under SunSystems 4.4 and higher:

 

SUN

password

<>

 

The following is an example macro that backs up the reference file and actuals ledger for a SunSystems database named DEM:

 

SUN

SUNSYS

<>

FB

B

DEM

Y

Y

<>

<>

<>

<>

<>

<>

<>

Y

X

 

The following is an example macro that performs a journal import up the reference file and actuals ledger for a SunSystems database named DEM:

 

SUN

SUNSYS

<>

LA

DEM

JI

<>

_DATA\{UNITY-SOURCE-FILE-NAME}

<>

<>

<>

<>

<>

<>

<>

<>

S

<>

X

X

 

Copyright © 2024 pasUNITY, Inc.

 

Send comments on this topic.