Search results for query: *

How about just defining the expected values as string variables and then comparing them to the actual checksums. I know what the expected values are. Would that be better? Also what would happen if the file did not exist?

Hank, this is a good start. I don't see where you are getting the expected values. Both of the values in the capture file are the actual values (i.e - the full path checksum and the FILE_TOTAL checksum are both actual checksums). I think there would need to be some kind of lookup table to...

The FILE_TOTAL is the actual checksum.

Hank, I would like the table to appear on my terminal. It should look something like this: Filename | Expected | Actual ------------------------------------ atlas2pega C7B52473 C7B52473 add_to_db 1F656216 1F656216 generic_add_db D6203F0B...

Here is the output of the capture file with 3 checksums. . The first line of each SUPERUSER prompt is the command and the rest is the output. Thanks in advance. SUPERUSER@adac:#[3] ascsum $PEGXBIN/atlas2pega * FILENAME CHECKSUM(CRC) *...

I need to write a script to gather the checksum values for a few different files and display them in a table format. I would like the table to be in this format: File Name Expected Actual atlas2pega 986C4452 986C4452 dicom2pega 1FCCC2221 5ER33345 etc...

That worked good. Here's my screen output (below). When I run my dicom_echo command it only uses the last entry (in this case it is ALI_Broker). Is there an easy modification which will allow me to test any 1 of these 6 entries (ALI_PACS, Adac_RTP, PACS_cube, etc...) Maybe have a user prompt...

the srtfmt command - that was just a typo. I have it correct in my script. However it is not running correctly. It compiles ok but it never actually runs. Is this the way it should be? proc main string sLine string hTok1 string nTok1 string pTok1 string gTok1 string dTok1 string...

knob, that worked perfectly. The delimited strings are all correct now. However when I try the strformat command i get an error: invalid expression token Command_Line and invalid string variable. Here is my syntax: srtfmt Command_Line "dicom_echo -c %s -t %s -v %s %s" dTok1...

Almost there. Here is what I'm getting now. It looks like fields 1 and 3 are correct but fields 2, 4 and 5 are truncating for some reason. Also, do I really have 30 string variables here? Can I use them in other scripts? It looks like we only defined 15 data strings. How do we end up with...

Getting closer... However the data strings are being repeated 5 times for each string. Here is an example: [Script]: proc main string sLine string hTok1 string nTok1,nTok2,nTok3 string szName = "Node_data.cap" clear set capture overwrite on set capture query...

That worked. The capture file looks good. How can see the values of the string variables?

By the way, I am assuming the Node_data.cap file is on my pc, not the remote host. If Node_data.cap is on the remote host would you still use fopen, since it is a Sun (unix) box?

I tried this. I'm still getting "error 5: invalid identifier". I verified my path (C:\files\Node_data.cap). I am using a modem connection. I have a separate script to set up my terminal. I checked my Node_data.cap file and it is empty. Other ideas?

I tried this but I am getting an "invalid identifier" error when the script runs. Here is what I have: proc main string sLine string hTok1 string nTok1,nTok2,nTok3 string pTok1,pTok2,pTok3 string gTok1,gTok2,gTok3 string dTok1,dTok2,dTok3 string Output transmit...

This is the command I am running and the output that follows: PEGASYS@adac_x:#[6] cat /vol/patients_db/dicom/dicompeers.cfg |egrep '%|node|port|calling|called' |fgrep -v # %ALI_PACS node = nserv0 port = 4000 callingAEtitle = ALI_STORE_SCP calledAEtitle =...

I am new to Aspect and I hope someone can get me started in the right direction. I am trying to capture several data strings and assign them to string variables. I will be getting the data from a Sun (Unix) server and need to know the best way to collect the data. Here is an example of what I...