dcsimg
Unable to use //DD:NAME in output= statement in SQL task
0 posts in topic
Flat View  Flat View
TOPIC ACTIONS:
 

Posted By:   rschramm
Posted On:   Thursday, February 6, 2014 05:56 AM

IBM's JVM implements special processing for files that are constructed with "//" at the beginning of the file name.  It allows for  MVS datasets and ddnames like datasets ("//x.y.z"), member names ("//x.y.z(m)"), ddnames ("//DD:ddname"), and dd member names ("//DD:ddname(member)"). When I run Ant in verbose, I see the message       [echo] Database Connection Test       [sql] connecting to jdbc:db2://servername:50000/database       [sql] Loading com.ibm.db2.jcc.DB2Driver using AntClassLoader with classpath /opt/db2luw/db2jcc4.jar        [sql   More>>

IBM's JVM implements special processing for files that are constructed with "//" at the beginning of the file name.  It allows for  MVS datasets and ddnames like

  • datasets ("//x.y.z"), member names ("//x.y.z(m)"),
  • ddnames ("//DD:ddname"), and dd member names ("//DD:ddname(member)").

When I run Ant in verbose, I see the message 

     [echo] Database Connection Test
      [sql] connecting to jdbc:db2://servername:50000/database
      [sql] Loading com.ibm.db2.jcc.DB2Driver using AntClassLoader with classpath /opt/db2luw/db2jcc4.jar 
      [sql] Opening PrintStream to output Resource /DD:TESTOUT
      [sql] 0 of 0 SQL statements executed successfully 
BUILD SUCCESSFUL

which appears that the output statement is being "fixed" and causing it to be invalid.  Is there a way to specify //DD:TESTOUT in such a way that it will not be "adjusted"?


 

Rob Schramm    <<Less
About | Sitemap | Contact