XSW: Procedure to generate an infile when NetBatch or MultiBatch is not installed

XSW: Procedure to generate an infile when NetBatch or MultiBatch is not installed


1.  Logon to the NonStop host as the XYGATESW (XSW) installation owner

2.  Volume to the XSW installation subvolume on the NonStop host

      Example:

      VOLUME $SYSTEM.XYGATESW

3.  Using EDIT or TEDIT, edit the SWCONF file and:
 
Change the line
 
BATCH_SCHEDULER NONE
 
To

BATCH_SCHEDULER $NONE

After making the change, exit the file.
 
4.  Via the XSW GUI, logon to the desired node and alter the Setup Collection Criteria.  Click on the Setup Collection Criteria tab at the top of the XSW GUI display and make the
     following changes:
 
2.1 Set Setup Collection Criteria
            
  Select Collection Type: Batch
           Batch Setup Parameters (Netbatch): Manual



 
5. Click on the Save button

     

 
 6. Click on the Submit button

      
     
 
This action will create a file called Netbatch.txt. This file can be ignored.
 
7. Create an edit file on the NonStop host with the following contents.
 
#frame
#push #informat
#SET #INFORMAT TACL
#push #defaults
volume <xsw-installation>
#push #assign
clear assign all
assign taclcstm,xyswcstm
#push #param
clear param all
PARAM XSWP1 "<collection-name>"
PARAM XSWP3 "<collection-name>"
PARAM XSWP4 [#defaults]
PARAM XSWP5 DEFAULT
PARAM XSWP7 $S.#X305.BATCH
PARAM XSWP20 [#processinfo/logonname/]
run xyswstrt
#pop #param
#pop #informat
#pop #assign
#pop #defaults
#unframe
 
Where:

<xsw-installation> = The location of the XSW host installation,  e.g.
                               \WINDY.$SYSTEM.XYGATESW
<collection-name> = Collection name as specified in the Collection Criteria in the GUI.

NOTE:  If you do not have a spooler collector of $S on your system, "$S.#X305.BATCH" should be modified to include a valid spooler collector name

 
8. Obey the file created in Step 4 on the NonStop host.   As this is a manual operation, the TACL session must remain available until the collection ends.  Do not terminate the
    TACL session until the collection has completed.

 
9.  Once it has completed, the collection may be downloaded manually from the GUI or an active Service Processor.

 

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

    • XSW: How to run a collection on a system that does not contain Netbatch or Multibatch.

      1. Setup and save a Collection Criteria via the GUI. 2. Create and Obey a file on the host with the following contents. #frame #push #informat #SET #INFORMAT TACL #push #defaults volume <xsw-installation> #push #assign clear assign all assign ...

    • XSW: Compliane Pro System.ArgumentOutOfRangeException Exception Error

      The solution requires installing a patched version of XSW, which is available through XYPRO or HPE Scout. The root cause of this issue is a datetime limit set to 12/31/2020 00:00:00 for a control that allows the user to schedule a Netbatch process. ...

    • XSW: All systems not appearing in XSW Collection Specifications display.

      Add the following NODE keyword for all systems where a collection is required. NODE \<nodename> $<vol>.<subvol> <nodename> is the name of the node from which XSW can collect information. <vol>.<subvol> is the volume and subvolume on that node where ...

    • XSW: How to create a XSW GUI installation log.

      All steps are not needed if upgrading. They are only needed if the installed PC version is the same we need an installation log file for. This gives good information for a complete re-installation. Completely uninstall XSW from this PC using the ...

    • XSW HelperService: Error183

      Workaround: Provide a proper email address on the Preferences form. Modify the email address on the Preferences Form to your_name@yourcompany.com. NOTE: This may cause an exception in the XSW Loader. However, the XSW Loader will complete the loading ...