setPAMtestid
Purpose:
-
Set the PAM Test ID
Enter:
-
setPAMtestid <testid> [datapoint] [id_extension] [path=/dir/path/]
Where:
-
testid
Required. Specify a 1-25 character PAM Test ID string. NOTE: If the first character of ‘testid’ is ‘@’, then ‘testid’ is the label of a STRING_VARIABLE that contains the testid value to be used.
datapoint
Optional. Specify an integer PAM datapoint number for NEXT PAM datapoint. Default = 1 for a new PAM Test ID or the NEXT datapoint number for an existing PAM Test ID. NOTE: The value of ‘datapoint’ is for the NEXT PAM datapoint that will be taken.
id_extension
Optional. The PAM testid extension that is a suffix to the testid to make up the complete PAM testid. If not entered, the current extension will not be changed. NOTE: If this argument is entered, the ‘datapoint’ argument must also be entered. The ‘!’ character that is part of the complete PAM testid should not be entered.
path
Optional. The path to the hold directory that is checked for any datapoint files. If any datapoint files exist, then the point number retrieved from the central node will be the last ‘successful’ datapoint and not the last datapoint taken at the testcell. This is to ensure that the datapoint will not be overwritten from an entry in the hold directory that gets processed later. If this argument is used, it must be the last argument. The default path is /data/pam/PAMdatapoint/hold/.
Example:
-
setPAMtestid myTestid
The above command sets the PAM Test ID to ‘myTestid’ and sets the PAM datapoint value so that the NEXT datapoint taken will have a value of 1. If it is an existing ID, then the next PAM Datapoint number will be determined from last point number assigned to that ID.setPAMtestid OldTestid 1997
The above command sets the current PAM Testid to OldTestid and the next PAM Datapoint to 1997. If 1997 is not the next point number for OldTestid , then a prompt asks if this number should be used. The next point number should not be a number that already exists in the PAM database.setPAMtestid @my_id 100
The above command sets the PAM Test ID to the value that is contained in the STRING_VARIABLE ‘my_id’. Assuming that variable had a value of ‘myTestid’, then the PAM Test ID would be set to ‘myTestid’ and the NEXT datapoint taken will have a value of 100.setPAMtestid myTestid 1 qsk19
The above command sets the PAM Test ID to ‘myTestid’ and the NEXT datapoint taken will have a value of 1 and the testid extension will be set to ‘qsk19’.setPAMtestid myTestid 1 qsk=19 path=/data/DARTS/PAMdatapoint/hold/
The above command sets the PAM Test ID to ‘myTestid’ and the NEXT datapoint taken will have a value of 1 and the testid extension will be set to ‘qsk19’. It will compare any files in the /data/DARTS/PAMdatapoint/hold/ directory to make sure no duplicate datapoint entries can be entered.setPAMtestid QSK2004 199 qk19
The above command sets the current PAM Testid to QSK2004 and the next PAM Datapoint to 199. If 199 is not the next point number for QSK2004 , then a prompt asks if this number should be used. The next point number should not be a number that already exists in the PAM database The extension of qk19 is used as the PAM Test ID extension making the complete PAM Test ID QSK2004!qk19.
Notes:
-
The setPAMtestid command enables change to the PAM Test ID that identifies subsequent datapoints in the PAM database. The optional datapoint argument sets the NEXT PAM Datapoint.
To create a new PAM Test ID, do not use the datapoint argument and the NEXT PAM Datapoint will be 1.
To reuse an old PAM TestID enter the TestID and the NEXT datapoint number will be determined from the existing data.
This command updates the PAM Test ID in the PAM Specs, updates the CyFlex Integer Variable for the PAM Datapoint, notifies the datapoint task of a change, and writes a new PAM header.