Colons are not valid in file names on Windows. Slashes aren't valid either, but as they also aren't on Unix, the tool seems to drop them.
Backslashes could be a real mess, as they mean completely different things on Unix vs. Windows. sas On Mon, May 1, 2017 at 1:59 PM, Dyck, Lionel B. (TRA) <[email protected]> wrote: > Tried it on Windows 10 bash shell and got a LOT of 'invalid argument' > messages on the ln command - but not on all. > > Example: > > ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_ > Server:_IP_Diagnosis_Guide.pdf’: Invalid argument > ln: failed to create symbolic link > ‘zOS_V2R2.0_Communications_Server:_SNA_Messages.pdf’: > Invalid argument > ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_ > Server:_IP_Messages_Volume_1_(EZA).pdf’: Invalid argument > ln: failed to create symbolic link ‘zOS_V2R2.0_Communications_ > Server:_IP_Messages_Volume_2_(EZB,_EZD).pdf’: Invalid argument > > > -------------------------------------------------------------------------- > Lionel B. Dyck > Mainframe Systems Programmer - TRA > Enterprise Operations (Station 200) (005OP6.3.10) > Information and Technology, IT Operations and Services > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
