The list also returned my message (it said something about sending the same message twice) but apparently both our messages appeared on the list anyway.
Regards, Alexander > -----Original Message----- > From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] > On Behalf Of Henrik Wahlstedt > Sent: zondag 11 juni 2006 20:35 > To: [email protected] > Subject: Select and SQL literal token - 'S', 2:nd try... > > > Hi, > > ADSM-L returned my message even tough Alexander have answered it... > And it isnt on the web so I resend it if some of you have any clue. > > //Henrik > > > -----Original Message----- > From: Henrik Wahlstedt > Sent: 9. juni 2006 10:52 > To: ADSM: Dist Stor Manager > Subject: Select and SQL literal token - 'S' > > > Hi, > > > If I use this select which I thought was OK before I tested it... > tsm:>select s.schedule_name, s.STARTTIME, a.node_name from > CLIENT_SCHEDULES s, ASSOCIATIONS a where > s.schedule_name=a.schedule_name > ANR2906E Unexpected SQL literal token - 'S'. > > | > > ...............................V............................... > ode_name from CLIENT_SCHEDULES s, ASSOCIATIONS a > where s.schedu > > ANS8001I Return code 3. > > > Instead of using S i use SS, and it works.. > select ss.schedule_name, ss.STARTTIME, a.node_name from > CLIENT_SCHEDULES > ss, ASSOCIATIONS a where ss.schedule_name=a.schedule_name > > > What magic lies behind "SQL literal token - 'S'." > Are there more tokens that I should be aware of? > Etc? > > > > Thanks > Henrik > > > ------------------------------------------------------------------- > The information contained in this message may be CONFIDENTIAL and is > intended for the addressee only. Any unauthorised use, > dissemination of the > information or copying of this message is prohibited. If you > are not the > addressee, please notify the sender immediately by return > e-mail and delete > this message. > Thank you. >
