<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: SVC99 Error in SAS Procedures</title>
    <link>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69276#M19882</link>
    <description>You will be best served by contacting SAS Support and open a track / issue with details about your error symptom, while providing sufficient documentation, complete SAS output listings, ISPF 3.2 dataset attribute information, and whatever is needed to substantiate your claim.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
    <pubDate>Wed, 25 May 2011 19:38:54 GMT</pubDate>
    <dc:creator>sbb</dc:creator>
    <dc:date>2011-05-25T19:38:54Z</dc:date>
    <item>
      <title>SVC99 Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69275#M19881</link>
      <description>Hello I am new to the forum and wanted to ask a question to see if anyone else has run into this issue.&lt;BR /&gt;
&lt;BR /&gt;
I just installed SAS 9.2 (TS2M3) across all our z/OS 1.10 &amp;amp; 1.12 environments.  It is working on all but one (in Europe).  The problem seems to be that they use 3 character VOLSER for their DASD.  When I run the following job I receive the following error: &lt;BR /&gt;
 &lt;BR /&gt;
ERROR: SVC99 error rc=C, reason=035C : IKJ56231I DATA SET MYDSN.CTLCARDS NOT ALLOCATED, SYSTEM OR INSTALLATION ERROR+IKJ56231I TEXT&lt;BR /&gt;
&lt;BR /&gt;
//DAGFRMAT DD DSN=MYDSN.CTLCARDS(AZDAGFMT) resides on a 3 character Volser and the .NEW version resides on a WORK** volser.  &lt;BR /&gt;
&lt;BR /&gt;
When I move the MYDSN.CTLCARDS to a 6 character volser (WORK**) so that both datasets are on 6 character VOLSER's it works fine.&lt;BR /&gt;
&lt;BR /&gt;
//SDTSJM01 JOB (1,18542,FMCC-1470),'SAS EURO TEST',      &lt;BR /&gt;
//      CLASS=T,MSGCLASS=9,REGION=4M,NOTIFY=&amp;amp;SYSUID      &lt;BR /&gt;
//*                                                      &lt;BR /&gt;
//SASSTEP    EXEC SASTEST,OPTIONS='NOSTAE VERBOSE'         &lt;BR /&gt;
//DAGFRCPY DD DSN=MYDSN.CTLCARDS.NEW(AZDAGFMT),DISP=SHR &lt;BR /&gt;
//DAGFRMAT DD DSN=MYDSN.CTLCARDS(AZDAGFMT),DISP=SHR          &lt;BR /&gt;
//SYSIN DD *                                             &lt;BR /&gt;
DATA _NULL_;                                             &lt;BR /&gt;
   INFILE DAGFRCPY;                                      &lt;BR /&gt;
   INPUT;                                                &lt;BR /&gt;
   LIST;                                                 &lt;BR /&gt;
RUN;                                                     &lt;BR /&gt;
DATA _NULL_;                                             &lt;BR /&gt;
   INFILE DAGFRMAT;                                      &lt;BR /&gt;
   INPUT;                                                &lt;BR /&gt;
   LIST;                                                 &lt;BR /&gt;
RUN;                                                     &lt;BR /&gt;
PROC OPTIONS VALUE;                                      &lt;BR /&gt;
RUN;                                                     &lt;BR /&gt;
%INCLUDE DAGFRCPY;                                       &lt;BR /&gt;
%INCLUDE DAGFRMAT;   &lt;BR /&gt;
&lt;BR /&gt;
has anyone experienced any issues with 3 character VOLSER's?</description>
      <pubDate>Wed, 25 May 2011 14:47:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69275#M19881</guid>
      <dc:creator>jmaitland</dc:creator>
      <dc:date>2011-05-25T14:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: SVC99 Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69276#M19882</link>
      <description>You will be best served by contacting SAS Support and open a track / issue with details about your error symptom, while providing sufficient documentation, complete SAS output listings, ISPF 3.2 dataset attribute information, and whatever is needed to substantiate your claim.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Wed, 25 May 2011 19:38:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69276#M19882</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2011-05-25T19:38:54Z</dc:date>
    </item>
    <item>
      <title>Re: SVC99 Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69277#M19883</link>
      <description>Thanks, already sent everything.  I was just checking to see if anyone else has run into this type of situation.</description>
      <pubDate>Thu, 26 May 2011 13:41:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69277#M19883</guid>
      <dc:creator>jmaitland</dc:creator>
      <dc:date>2011-05-26T13:41:44Z</dc:date>
    </item>
    <item>
      <title>Re: SVC99 Error</title>
      <link>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69278#M19884</link>
      <description>Honestly, in my 30+ years experience with current IBM mainframe z/OS and legacy MVS environments, I have never seen a DASD VOLSER defined that was less than six characters -- how odd.&lt;BR /&gt;
&lt;BR /&gt;
Scott Barry&lt;BR /&gt;
SBBWorks, Inc.</description>
      <pubDate>Thu, 26 May 2011 13:52:30 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Procedures/SVC99-Error/m-p/69278#M19884</guid>
      <dc:creator>sbb</dc:creator>
      <dc:date>2011-05-26T13:52:30Z</dc:date>
    </item>
  </channel>
</rss>

