> > And maybe it's just plain ol' broken. *I* don't know. :-) Hopefully the > Developerworks folks will post back soon. > I may be wrong here since I can't try it, but I think it is broken. The replace_char() routine should probably be replacing ALL dashes with 0x0a characters. As coded, it's only replacing the first one.
If you look at the example Rexx code in the manual, when a name is retrieved from the HMC/SE, the Rexx code converts ALL line feeds to spaces. /*****************************************************************/ /* Get the object name attribute. */ /*****************************************************************/ rc = RxHwmcaGet(¹INITBLK.¹,ATTRID,OUTPUT.,api_timeout) if rc == HWMCA_DE_NO_ERROR then do /**************************************************************/ /* Remove any newline characters from the name. */ /**************************************************************/ name = translate(OUTPUT.1.DATA,¹ ¹,¹0A¹x); End That, and the fact that snIPL is worried about dashes so much, leads me to believe the HMC/SE will convert any dashes to LFs before sending them out. Since the name in question has an extra dash in it, the HMC is probably sending (Rexx format): "P0012345" || '0a'x || "CCPUC" || '0a'x || "LX2" Whereas snIPL would be using: "P0012345" || '0a'x || "CCPUC-LX2" So, when comparing the user requested name and to the ones retrieved from the HMC/SE, taint nuttin' gonna match. But again, that's just me supposin' and the DW folks will probably laugh. :-) Leland ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
