DESTID FADDRESn value not refreshed by REINIT
Document ID :
Last Modified Date :
Show Technical Document Details
The path of a FTP node was updated and the REINIT command issued but the file seems to still be using the old path.
The FADDRESx parameter values are supposed to be refreshed by a REINIT command. What may happen is that files that were already in spool are not affected by the change. Any files created AFTER you issued the REINIT commands should have the new values. The DESTID statements affect files only at creation time. This is the normal behavior.
However, there is a CA Spool 12.0 fix for a problem that may cause DESTID statements to be ignored in case you issued the command REINIT,PRT. The fix is SO06643.
You can use the DD command to display the current value of the DESTID statements. See reference below:
For example, if you have a DESTID statement like below:
DESTID QDEST=FILCAFTP, FADDRES1='FILENAME=/&FNM.&DAY.&TIM.TXT', FADDRES2='FTPUSER=anonymous,FTPPASSfirstname.lastname@example.org',
You can use the command below on the console:
where caspoolstc is the name of the CA Spool started task. Or from the CA Spool menu: /DD,D=FILCAFTP.
ESF890 DESTID QDEST=FILCAFTP,
Lastly, it may be possible for you to use DRIVPRMx keywords in the NODE statement instead of the DESTID statements. This will work unless you really need to override the value of the OUTPUT ADDRESS JCL keyword. Taking my DESTID statements above as an example, the NODE definition would be:
Was this information helpful?