XAC: NSGIT fails to start with error 4006

XAC: NSGIT fails to start with error 4006

The following config will redirect OSH output to the parent TTY which is the Guardian terminal.

Syntax:
nsgit config --global nsgit.osstty.redirectif=pattern

Example:

The following makes the redirect conditional, only if runs via XAC. So pure TACL won't invoke the above redirect.

nsgit config --global nsgit.osstty.redirectif=\*.$*.*.xygateac

The name=value pair for NSGit needs to be supplied as a single command line argument, which is why the first entry for redirect=parent worked. Alternatively you can edit the ~/.nsgit.config file using an editor in the OSS side, as documented. You can also edit this file in GUARDIAN using the nsgit export-oss and nsgit import-oss commands to move the contents in and out of the OSS file system.

If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.
 

    • Related Articles

    • XMA: SLSENDER fails to start after upgrading to Merged Audit 2.65

      There is a known issue where SLSENDER will not start after upgrading to XMA 2.65. If the customer cannot start SLSENDER after upgrading, the post upgrade steps below can be used. If we know a customer will be upgrading to XMA 2.65, pre-upgrade steps ...

    • XMA: The SQLXPress mover fails with error 48 (security Violation).

      Start SQLEXpress with the same user id that started XMA, or re-secure the object shown in the error message for access by the user id that started XMA. If this article did not provide a solution, please open a case with our support team by sending an ...

    • XMA: XMA_MANAGER macro fails with [Check_SQLCompileNeeded] error

      The XMA SQL database needs to be recompiled for this error to be resolved. 1) stop XMA XMA_PWSTOP 2) Update the database statistics and re SQLCOMPILE all the XMA programs XMA_SQLCOMPALL 3) Start XMA XMA_PWCOOL If you are unable to locate the solution ...

    • XMA: Can't start iTP Webserver Mover - SQL Error

      Probable cause is that the iTP webserver mover is attempting to process a file type that is not yet supported. Several file formats are not currently supported by the iTP mover: HTTPD log support. The format is not CLF format but a hybrid of access ...

    • XAC: Resizing XYGATEAC Logs

      To resize using the new EXT, stopping all XAC sessions and restarting them is an essential step because if the audit file is still opened by a previous session, then the old audit parameters are stored in memory until the existing sessions are ...