The below command was successful, as there was a file matching the file patternĮxecuted: cat -s /staging/GDW_DEV/stage_fil es/sf/MPS/ ORDERS_*.p ipe > /staging/GDW_DEV/stage_fil es/sf/MPS/ ORDERS. Installing Datastage EE 7.5. SAP PowerDesigner PDM 7.5 to 16.x - Import. Below is snipet from the DataState logĮxecuted: cat -s /staging/GDW_DEV/stage_fil es/sf/ufor got.txt > /staging/GDW_DEV/stage_fil es/sf/MPS/ ORDERS.csvĬommand cat did not finish OK, reply = '2' Subscription Bridge Specifications Vendor IBM Tool Name InfoSphere DataStage Tool Version 7.5 to 11.x Tool Web Site. I suspect that an error is thrown, but putty is ignoring the error, whereas Datastage is not ignoring the error. The -s parameter means to suppress messages about non-existant files. Datastage 7. My company is on DataStage 7.5 and unix Solaris However, it will work in Datastage and putty if the specified file or wildcarded file (u*.txt) exists.Ĭat -s /staging/GDW_DEV/stage_fil es/sf/ufor got.txt > /staging/GDW_DEV/stage_fil es/sf/MPS/ ORDERS.csv ![]() Enter the parameter names again where specified. Workaround Edit the job activity stages in the job sequence. There is no file with the name "uforgot.txt" in the specified folder. Job sequences from releases before DataStage 7.5 that use jobs which rely on job parameters do not run following import into a post-7.5.1 system. ![]() The following command will work under putty, but not within the datastage execute command.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |