FUSSMEM

You can use the FUSSMEM exec to send multiple members of a PDS to a remote platform server node.

You can select which members of the PDS are sent by specifying a wildcard within the member name. The PDS file and optionally the member name are specified in the LFILE parameter. For example, 

LFILE=MY.PDS(MEMBERS) RF=C:\PROD\ACCT\MEMBER.TXT 
IPPORT=46464 IPADDR=127.0.0.1

If no member name is defined within the parentheses in the LFILE parameter, all members are selected. Up to 1000 members can be selected. If you select more than 1000 members, a message is displayed and no transfer is queued.

Wildcard Parameters

Fusion supports the following wildcard parameters:

  • *: represents a string of unspecified characters.
  • ?: represents a single unspecified character.

You can use both of these parameters in a member name. For example:

LFILE=PROD.SOURCE(A??B*).

In this example, all members starting with A in position one and B in position four are sent.

Substitutable Parameter

You can use the %MEM substitutable parameter in the RFILE parameter. In this case, the platform server substitutes the member name for the %MEM parameter.

For example, when members ABC123 and XYZ456 are selected and RFILE=C:\prod\acct\%mem.asm is specified, the output is as follows: 

RFILE=C:\prod\acct\ABC123.asm
RFILE=C:\prod\acct\XYZ456.asm

If the %MEM parameter is not defined in the RFILE parameter, the platform server adds the member name to the end of the RFILE parameter. If the RFILE parameter does not end in a backslash (\), the platform server adds a backslash before adding the member name to the end of the RFILE parameter.

For example: 

FUSSMEM IPADDR=127.127.127.1 IPPORT=46464 LF=LOCAL.PDS.FILE RF=C:\%MEM.TXT 
INTERVAL=3 SAY WAIT

The output of this example is as follows: 

TRANSACTION=IA01500043 STATUS=ACTIVE   RECORD=000000000 BYTES=000000000
TRANSACTION=IA01500043 STATUS=COMPLETE RECORD=000000017 BYTES=000001360
***Fusion retcode.......=  0
***Fusion TransNum......=  IA01500043
***Completed transfers..=  01
***Successful transfers.=  01
***Failed transfers.....=  00
***Purged transfers.....=  00
***Last Message.........=  PGTF3101I Activity IA01500043 successfully
transferred 17 records with remote node 127.127.127.1
Request Queued successfully with TRANSNUM= IA01500043 for Member: MEMBER1
Note: This output is received for each member of the PDS.

The TEST Parameter

When you use the TEST parameter in the FUSSMEM exec, the exec displays and tests the LFILE and RFILE parameters to be passed to the platform server instead of queuing the request. It is good practice to add this parameter when creating new requests to ensure that the correct members are sent and the correct RFILE names are created. After you verify that all the information of the exec is correct, you can remove the TEST parameter, and schedule the file transfers.

For example,

FUSSMEM LF=MY.PDS RF=C:\ACCT\%MEM.TAX TEST NODE=NODE1

If two members are in the MY.PDS file, the output of this example is as follows: 

LFILE=MY.PDS(NY2008)  RFILE=c:\acct\NY2008.tax
LFILE=MY.PDS(FED)     RFILE=c:\acct\FED.tax
Note: No transfers are queued when the TEST parameter is on the command line. After you validate that the parameters are correct, you can remove the TEST parameter and execute the FUSSMEM command.

The WAIT and MWAIT Parameters

You can use the WAIT and MWAIT operands in this exec. The platform server only supports to queue up to 40 transfers before a FUSWAIT command is executed for an address space. 

FUSSMEM IPADDR=127.127.127.1 IPPORT=46464 LF=LOCAL.PDS.FILE RF=C:\%MEM.TXT 
INTERVAL=3 SAY WAIT TEST

In this example, the FUSSMEM exec shows the remote file name that is resolved, but does not perform the transfer.

The output of this example is as follows: 

LFILE=LOCAL.PDS.FILE(MEMBER1)  RFILE=C:\MEMBER1.txt
LFILE=LOCAL.PDS.FILE(MEMBER2)  RFILE=C:\MEMBER2.txt
LFILE=LOCAL.PDS.FILE(MEMBER3)  RFILE=C:\MEMBER3.txt
LFILE=LOCAL.PDS.FILE(MEMBER4)  RFILE=C:\MEMBER4.txt