ftp-fileset protocol outbound problem setting filename

Here is the msgdump from the failed attempt.  Notice the value in the msgDriverControl is the value I am passing to it.

msg: 0x0204BCB4

   msgType           : DATA

   msgClass          :

   msgState          : Unknown: 0 (0)

   msgPriority       : 5120

   msgRecoveryDbState: Log:off (1)

   msgFlags          : 0x2

   msgMid            : [0.0.0]

   msgSrcMid         : midNULL

   msgSrcMidGroup    : midNULL

   msgHostId         : 4028562964

   msgOrigSrcThread  :

   msgOrigDestThread :

   msgSrcThread      :

   msgDestThread     :

   msgXlateThread    :

   msgSkipXlate      : 0

   msgSepChars       :

   msgNumRetries     : 0

   msgGroupId        : 0

   msgDriverControl  : {FILESET {{OBFILE 3100069429.txt}}}

   msgRecordFormat   :

   msgRoutes         :

   msgUserData       :

   msgStaticIsDirty  : 0

   msgVariableIsDirty: 1

   msgTimeStartIb    : 1466801162.528

   msgTimeStartOb    : 1466801162.528

   msgTimeCurQueStart: 0.000

   msgTimeTotalQue   : 0.000

   msgTimeRecovery   : 1466801162.528

   msgEoConfig       : 0x00000000

   msgData (BO)      : 0x0204BDB8

Please disregard this post.  I discovered the problem.  I was testing the proc with and HL7 message and those instances worked.  When I attempted to use this script in the route it was failing because the message was altered by the time it reached my proc.  Thus there was no value in PID-3 to pull because the message was no longer formatted like an HL7.

Here are the details of this solution for anyone who needs to:

1. Take an inbound HL7 message

2. Parse this message and store specific pieces of data in METADATA USERDATE

3. Format this HL7 to a readable document using a VRL

4. FTP this document to a server with the data from the USERDATA as the filename.

5. Each message gets it own named text document

Interface description

Script on the inbound thread that stores the value from PID-3 in the USERDATA key

XLATE for the conversion of the HL7 to the VRL format

Script that takes the data from the USERDATA key and assigns it to the OBFILE key.  This is what names the outbound file.

Here is a sample of the output