RXS_cmpTransFile()
In the process of doing web services you will most likely run across the need to create many files in the IFS, and each of those files must be uniquely named if you don’t want one to over write the next. Instead of doing several concatenations of strings and dates and numbers to come up with a unique file name, use RXS_cmpTransFile().
Basically, a programmer tells the function the file extension (i.e. .xml), the separator for each piece of information in the file name (up to 4) that will be passed to it (i.e. _).
Typical usage would look like:
gReqFile = RXS_cmpTransFile('_': '.xml': RXS_UnqNbr : 'req');
This produces a string with the contents /www/myrxs/trans/99999_req.xml where 99999 is the next sequential number in data queue RXS/RXSUNQ, and ‘/www/myrxs/trans/’ is the value stored in column TRANSDIR in table RXSCFG.
Subprocedure Prototype
|
Creates a unique IFS file path. |
|
Required The value to be used as the separator between each of the file path components passed in pVal1-5. |
|
Required The extension of the file path to be generated, including the period. Example: |
|
Required Character data to be used in building the unique file path. Can accept character data, or either RXS_UnqNbr() or RXS_Timestamp(). |
|
Character data to be used in building the second segment of the unique file path. Can accept character data, or either RXS_UnqNbr() or RXS_Timestamp(). |
|
Character data to be used in building the third segment of the unique file path. Can accept character data, or either RXS_UnqNbr() or RXS_Timestamp(). |
|
Character data to be used in building the fourth segment of the unique file path. Can accept character data, or either RXS_UnqNbr() or RXS_Timestamp(). |
|
Character data to be used in building the fifth segment of the unique file path. Can accept character data, or either RXS_UnqNbr() or RXS_Timestamp(). |