instructions_ossrvsched_head.txt=<h3>${iomsrv.ossrvsched.name}</h3> ${line.separator}\


instructions_ossrvsched_head_migrated.txt=<h3>Operating System Services</h3> ${line.separator}\


instructions_ossrvsched_details_table_head.txt=<table class="detailTable" border=0 cellPadding=0 cellSpacing=0> ${line.separator}\


instructions_ossrvsched_details_migrated_servers.txt=<tr> ${line.separator}\
    <td class="detailLabel">Servers Migrated</td> ${line.separator}\
    <td class="detailContent">${migrated.servers.names}</td> ${line.separator}\


instructions_ossrvsched_details_host.txt=<tr> ${line.separator}\
    <td class="detailLabel">Host machine</td> ${line.separator}\
    <td class="detailContent">${iomsrv.ossrvsched.host}</td> ${line.separator}\
  </tr> ${line.separator}\


instructions_ossrvsched_details_ports.txt=<tr> ${line.separator}\
    <td class="detailLabel">Ports</td> ${line.separator}\
    <td class="detailContent">${migrated.servers.ports}</td> ${line.separator}\
  </tr> ${line.separator}\


instructions_ossrvsched_details_port.txt=<tr> ${line.separator}\
    <td class="detailLabel">Port</td> ${line.separator}\
    <td class="detailContent">${iomsrv.ossrvsched.port}</td> ${line.separator}\
  </tr> ${line.separator}\


instructions_ossrvsched_details_logging.txt=<tr> ${line.separator}\
    <td class="detailLabel">Log directory</td> ${line.separator}\
    <td class="detailContent"><a href="file://${ossrvsched.logs.dir}">${ossrvsched.logs.dir}</a> ${line.separator}\
  </tr>  ${line.separator}\


instructions_ossrvsched_details_log_dirs.txt=<tr> ${line.separator}\
    <td class="detailLabel">Log directories</td> ${line.separator}\
    <td class="detailContent"> ${migrated.servers.log.dirs} ${line.separator}\
  </tr>  ${line.separator}\


instructions_ossrvsched_details_validation.txt=<tr> ${line.separator}\
    <td class="detailLabel">Validation steps</td> ${line.separator}\
    <td class="detailContent">${line.separator}\
      <ol> ${line.separator}\
          <li>In the SAS Management Console, on the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
          <li>Highlight ${iomsrv.ossrvsched.name}.</li> ${line.separator}\

instructions_ossrvsched_details_validation_migrated.txt=<tr> ${line.separator}\
    <td class="detailLabel">Validation steps</td> ${line.separator}\
    <td class="detailContent">${line.separator}\
      <ol> ${line.separator}\
          <li>In the SAS Management Console, select "${migrated.server.repository.name}" repository.</li> ${line.separator}\
          <li>On the Plug-ins tab, select "+" to expand the Server Manager node.</li> ${line.separator}\
          <li>Highlight ${migrated.servers.server.context}.</li> ${line.separator}\

instructions_ossrvsched_details_validation_sasdemo.txt=<li>Right mouse click this server and select Validate (you can enter ${oma.person.demo.login.userid} for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_ossrvsched_details_validation_sassrv.txt=<li>Right mouse click this server and select Validate (you can enter the SAS Spawned Servers account for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_ossrvsched_details_validation_sasdemosassrv.txt=<li>Right mouse click this server and select Validate (you can enter ${oma.person.demo.login.userid} or the SAS Spawned Servers account for the user ID). You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_ossrvsched_details_validation_novaliduser.txt=<li>Right mouse click this server and select Validate. You can enter a user ID and password that meet all of these requirements: ${line.separator}\
  <ol> ${line.separator}\
    <li>the account is known to the host of the scheduling server. (An ID that ends in @saspw does not meet this requirement.)</li> ${line.separator}\
    <li>the account has the Windows right Log on as a batch job (if the server is on Windows).</li> ${line.separator}\
    <li>the account has a corresponding metadata identity.</li> ${line.separator}\
  </ol> ${line.separator}\
You should see a <i>Validation Successful</i> message.</li> ${line.separator}\

instructions_ossrvsched_details_validation_migrated_1.txt=<br> ${line.separator}\
    <br> Repeat all the above steps for the following servers\
    <br><table border=1><tr><th>Repository </th><th> Server</th></tr>\
    ${migrated.servers.list}</table>\

instructions_ossrvsched_details_validation_tail.txt=</ol> ${line.separator}\
    </td> ${line.separator}\
  </tr>  ${line.separator}\

instructions_ossrvsched_details_table_tail.txt=</table>  ${line.separator}\

instructions_ossrvsched_details_notes_head.txt=<h4>Notes:</h4> ${line.separator}\
<ul> ${line.separator}\

instructions_ossrvsched_details_log4sas.txt=<li>The ${ossrvsched.logs.dir} directory is intended to serve as a placeholder for scheduling server logs. Scheduling server logs may be directed to this directory in the event that your SAS or IT administrator enables logging. The following default attributes are associated with the Logs directory: ${line.separator}\
    <ul> ${line.separator}\
      <li>The Logs directory serves as a placeholder should you enable logging for scheduling servers</li> ${line.separator}\
    </ul> ${line.separator}\
    <br class="br">Enabling scheduling server extra logging should be carefully considered, due to the proliferation of scheduling server logs.  To enable scheduling server logging, perform the following steps: ${line.separator}\
    <ul> ${line.separator}\
      <li>Add -logconfloc option to use logconfig.xml</li> ${line.separator}\
      <li>Modify the scheduling server logconfig.xml to enable the desired levels of logging</li> ${line.separator}\
      <li>Alternately, enable the logconfig.trace.xml logging file to capture scheduling server diagnostic logging</li> ${line.separator}\
    </ul> ${line.separator}\
</li>${line.separator}\

instructions_ossrvsched_details_log4sas_migrated.txt=<li>The directory or directories shown above are intended to serve as a placeholder for scheduling server logs. These logs may be directed here in the event that your SAS or IT administrator enables logging. The following default attributes are associated with a given Logs directory: ${line.separator}\
    <ul> ${line.separator}\
      <li>The Logs directory serves as a placeholder should you enable logging for scheduling servers</li> ${line.separator}\
    </ul> ${line.separator}\
    <br class="br">Enabling scheduling server logging should be carefully considered, due to the proliferation of scheduling server logs, as well as the requirement to grant universal write access to a given Logs directory.  To enable scheduling server logging, perform the following steps: ${line.separator}\
    <ul> ${line.separator}\
      <li>Add -logconfloc option to use logconfig.xml</li> ${line.separator}\
      <li>Modify the scheduling server logconfig.xml to enable the desired levels of logging</li> ${line.separator}\
      <li>Alternately, enable the logconfig.trace.xml logging file to capture scheduling server diagnostic logging</li> ${line.separator}\
    </ul> ${line.separator}\
</li>${line.separator}\

instructions_ossrvsched_details_notes_tail.txt=</ul>  ${line.separator}\

instructions_ossrvsched_start_Windows.txt= &nbsp; ${line.separator}\

instructions_ossrvsched_start_Unix.txt= &nbsp; ${line.separator}\

instructions_ossrvsched_start_Zos.txt= &nbsp; ${line.separator}\

errors_ossrvsched_head.txt=<h3>Operating System Services failed to deploy successfully</h3>

errors_ossrvsched_list_head.txt=<ol> ${line.separator}\

errors_ossrvsched_backup.txt=<li><p>Backup of files in both ${error.srcdir} and ${error.deploydir} failed. The directory may be read only, the directory may not exist, or the permissions are insufficient for this process. ${line.separator}\
  <ul>  ${line.separator}\
    <li>Error log file: <a href="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\    
    <li>Scheduling server logs: <a href="file://${ossrvsched.logs.dir}" type="text/plain" target="_blank">${ossrvsched.logs.dir}</a></li>  ${line.separator}\ 
  </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_ossrvsched_copyOrigFiles.txt=<li><p>The copying and configuring of files from ${error.srcdir} to ${error.deploydir} failed. ${line.separator}\
  <ul>  ${line.separator}\
    <li>Error log file: <a href="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\    
    <li>Scheduling server logs: <a href="file://${ossrvsched.logs.dir}" type="text/plain" target="_blank">${ossrvsched.logs.dir}</a></li>  ${line.separator}\ 
  </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_ossrvsched_loadMetadata.txt=<li><p>Information about the scheduling server could not be loaded into the metadata server. ${line.separator}\
  <ul>  ${line.separator}\
    <li>Error log file: <a href="file://${error.logfile}" type="text/plain" target="_blank">${error.logfile}</a></li>  ${line.separator}\
    <li>Scheduling server logs: <a href="file://${ossrvsched.logs.dir}" type="text/plain" target="_blank">${ossrvsched.logs.dir}</a></li>  ${line.separator}\
  </ul></p>  ${line.separator}\
</li>  ${line.separator}\

errors_ossrvsched_list_tail.txt=</ol> ${line.separator}\

unconfiguration_ossrvsched_summary_head.txt=<h3>Operating System Services</h3> ${line.separator}\

unconfiguration_ossrvsched_summary_item.txt=<p>The scheduling server was removed.</p> ${line.separator}\
   <ul> ${line.separator}\
      <li>${ossrvsched.configobj.name} was removed from metadata.</li> ${line.separator}\
   </ul> ${line.separator}
