Use this utility to test the transfer of files to and from IDS. Here is an example of the syntax and parameters for this utility:
Note | By default, the DSITEST utility runs in Java mode. You can, however, run it in C mode. To switch modes, open DSITEST in a text editor and follow the instructions at the beginning of the script. |
dsitestw /time /waitonlast / display /nowait /reqtype /msg /notrans /noattachs /norcvs /atcfile /rcvfile
Parameter |
Description |
Time |
Displays total seconds for all operations. Do not include NoRCVs, ATCFile, or RCVFile with this parameter because those parameters contain user prompts that affect the time. |
WaitOnLast |
Waits on the last message before capturing the ending time. |
Display |
Displays the resulting DSI Soap XML message that contains the name/value pairs for each transaction. |
NoWait |
Do not wait for the server before adding next message to queue. |
ReqType |
The IDS request type. The default is SSS. |
MSG |
The name of the file that contains the request name/value pairs. |
NoTrans |
The total number of transactions to process. |
NoAttachs |
The total number of file attachments to send per transaction using the DSISendFile API. If you include this parameter, the program expects an input file named SENDFILES.MSG that contains the information for each attachment to send. |
NoRCVs |
The total number of file attachments to receive per transaction via the DSIReceiveFile API. If you include this parameter, the program expects an input file named RECEIVEFILES.MSG that contains the information for each attachment to receive. |
ATCFile |
A single file attachment to send via the DSISendFile API. The program prompts the user for the attachment ID, file name, and encoding type. |
RCVFile |
A single file attachment to receive via the DSIReceiveFile API. The program prompts the user for the attachment ID and file name. |
Neither the case nor the order of the parameters is important. |
You can include these parameters on the command line or place them in an input file named PARAMS.MSG. On the command line, separate parameters with slashes (/), dashes (-), or spaces:
DSITESTW /time=yes
DSITESTW -time=yes
DSITESTW time=yes
If you include the parameters in the PARAMS.MSG file, format them as shown in this example of the PARAMS.MSG file:
time=yes
waitonlast=no
display=yes
nowait=no
reqtype=LGN
notrans=50
msg=prt.msg
noattchs=0
norcvs=0
atcfile=yes
rcvfile=yes
Here is an example of how you could execute this program from the command line:
dsitesw time=yes display=yes notrans=2 reqtype=prt msg=c:\prt.msg
Here is an example of the PRT.MSG file:
USERID=FORMAKER
Arckey=00345A0D5600000008
reqtype=PRT
config=UTILITY
company=1199999
lob=Lee
policynum=Roswell, Ga 30015
rundate=021705
printpath=\10.8.10.137\Websrvr_client\html
If the NoAttachs parameter is greater than zero, the program expects an input file named SENDFILES.MSG which contains a list of the attachments to send. Use either NoAttachs or ATCFile, but not both.
Use the ATCFile parameter when you only want to send one file attachment. The ATCFile parameter uses command line parameters for the attachment ID, file name, and encoding type. Here is an example of the ATTACHMENTS.MSG file:
name=UTILITYINI
file=X:\IDS\AddlSrvrs\utility.ini
type=TEXT
name=TESTPDF
file=X:\websrvr_client\html\test.pdf
type=BINARY
If the NoRCVs parameter is greater than zero, the program expects an input file named RECEIVEFILES.MSG, which contains a list of attachments to receive. Include either NoRCVs or RCVFile, but not both.
Use the RCVFile parameter when you only want to receive one attachment. The RCVFile parameter uses command line parameters for the attachment ID and file name. Here is an example of the RECEIVEFILES.MSG file:
name=PDFFILE1
file=X:\\IDS\\AddlSrvrs\\Output\\file1.pdf
name=PDFFILE2
file=X:\\IDS\\AddlSrvrs\\Output\\file2.pdf
If you omit the request type from the command line or the PARAMS.MSG file, the program uses SSS as the default request type.
© Copyright 2012, Oracle and/or its affiliates. All rights reserved. Legal notices.