GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E

i

CUSTOMER SERVICE BULLETIN

DPS 7000

GCOS 7-V11

TS 9940 UP10

GCOS 7 R&D

*** SEPTEMBER 2009 ***

© Bull S.A.S 2006-2009

This document is issued for information purposes only. It does not involve Bull S.A.S. responsibility in case of damage resulting from its implementation.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 1

TABLE OF CONTENTS 1 INTRODUCTION .............................................................................................................................4

1.1 SCOPE OF THIS CUSTOMER SERVICE BULLETIN ..............................................................................4 1.2 PRESENTATION OF THE CUSTOMER SERVICE BULLETIN (CSB) .....................................................4 1.3 NOTICE ................................................................................................................................................5 1.4 PREVIOUS VERSIONS OF THE CSB .....................................................................................................5 1.5 CURRENT VERSION OF THE CSB........................................................................................................5

2 INSTALLATION RULES OF GCOS 7-V11 TS 9940 ........................................................................6 2.1 FIRST INSTALLATION ON XTA OR NS PLATFORMS .....................................................................7 2.2 UPDATING PROCEDURE ......................................................................................................................8

2.2.1 Delivery of Technical Status and Patch-media on CD-ROM for XTA or NS-SYSTEMs....................... 10 2.2.2 Running the DETECT_SITE Utility ........................................................................................................ 11 2.2.3 Prerequisites ............................................................................................................................................. 11 2.2.4 Installing the Technical Status.................................................................................................................. 11 2.2.5 Checking Transferred Patches .................................................................................................................. 12 2.2.6 INIT of the System ................................................................................................................................... 12 2.2.7 Restarting the System ............................................................................................................................... 12 2.2.8 SECUR’ACCESS..................................................................................................................................... 13 2.2.9 RDDF 7-V2 .............................................................................................................................................. 13 2.2.10 Restarting Production ............................................................................................................................... 14

2.3 TECHNICAL STATUS DOCUMENTATION..........................................................................................15 2.4 DISK SPACE OCCUPANCY.................................................................................................................15 2.5 IDENTIFICATION OF GCOS 7-V11 TS 9940 IN THE BANNERS........................................................15

3 REMINDER ON CHANGES INTRODUCED FROM GCOS 7-V9 TS 9866 TO GCOS 7-V10 TS 9930, INCLUDED IN GCOS 7-V11 TS 9940 .................................................................................................16

3.1 VISIBILITY CHANGES INTRODUCED BY GCOS 7-V9 TS 9866 OR GCOS 7-V10 TS 9870.............16 3.1.1 GCL COMMAND MDLD CLASSLIST PARAMETER ........................................................................ 16 3.1.2 OCS DRIVER LOAD MODULES .......................................................................................................... 16

3.2 IMPROVEMENTS INTRODUCED IN GCOS 7-V9 TS 9866 OR GCOS 7-V10 TS 9870 .....................17 3.2.1 NEW KEYWORD ERASE OF GPL PRIMITIVE H_DEALLOC.......................................................... 17 3.2.2 Standard GPL primitives .......................................................................................................................... 17 3.2.3 TDS – TCP/IP option DATACONVERT ................................................................................................ 17 3.2.4 TDS - TCP/IP FUNCTION BREAK........................................................................................................ 17 3.2.5 TDS – TCP/IP API for 3-tiers architecture with NT server ..................................................................... 17 3.2.6 Improve TDS maximum declared transactions number ........................................................................... 17 3.2.7 GCOS 7 GTWRITER support of 15000 declared terminals .................................................................... 17

3.3 VISIBILITY CHANGES INTRODUCED IN GCOS 7-V10 TS 9910.......................................................18 3.3.1 TDS TRACE PRINT................................................................................................................................ 18 3.3.2 ARM: improvement in messages.............................................................................................................. 18

3.4 IMPROVEMENTS INTRODUCED IN GCOS7-V10 TS 9910 ...............................................................18 3.4.1 TDS .......................................................................................................................................................... 18 3.4.2 Extension of proxy access rights .............................................................................................................. 19 3.4.3 NEW LM H_VOLCHECK ...................................................................................................................... 19 3.4.4 Copy files for LIST_VOLUME or LIST_FILE OUTFILE contents ....................................................... 19

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 2

3.4.5 GTWRITER..............................................................................................................................................19 3.4.6 Dynamic save: improvement of error message .........................................................................................19 3.4.7 COBOL: new option NCKUKFIL to compile a tpr..................................................................................19 3.4.8 IOF: clean user’s mailbox .........................................................................................................................19 3.4.9 Config: new parameter lines for jobclass statement..................................................................................20 3.4.10 C LANGUAGE: improve MALLOC and FREE......................................................................................20 3.4.11 Access to user’s label from cobol .............................................................................................................20 3.4.12 RFC1006...................................................................................................................................................20

3.5 VISIBILITY CHANGES INTRODUCED IN GCOS 7-V10 TS 9920...................................................... 20 3.5.1 GTWRITER..............................................................................................................................................20

3.6 IMPROVEMENTS INTRODUCED IN GCOS7-V10 TS 9920............................................................... 21 3.6.1 TDS...........................................................................................................................................................21 3.6.2 GTWRITER..............................................................................................................................................21 3.6.3 DJP............................................................................................................................................................21 3.6.4 Job Management .......................................................................................................................................21 3.6.5 GIUF .........................................................................................................................................................21 3.6.6 MAINTAIN LIBRARY SM .....................................................................................................................21

3.7 VISIBILITY CHANGES INTRODUCED IN GCOS 7-V10 TS 9930...................................................... 21 3.7.1 ARM .........................................................................................................................................................21 3.7.2 H_VOLCHECK........................................................................................................................................22

3.8 IMPROVEMENTS INTRODUCED IN GCOS7-V10 TS 9930............................................................... 22 3.8.1 TDS...........................................................................................................................................................22 3.8.2 DP_SAVE.................................................................................................................................................22 3.8.3 SWLOG ....................................................................................................................................................22 3.8.4 WRITER QUEUED..................................................................................................................................22

4 VISIBILITY CHANGES INTRODUCED BY DPS 7000/XTA OR NS700X OR NOVASCALE/G7XX .. 23 4.1 CUSTOMER DATA MIGRATION.................................................................................................. 23

4.1.1 Compatibility rules between former DPS 7000 and DPS 7000/XTA or NS 700x or NovaScale/G7xx platforms 23 4.1.2 User DATA BASE Evolution ...................................................................................................................23 4.1.3 GCOS 7 Disk File .....................................................................................................................................24 4.1.4 Migration of System files..........................................................................................................................24

4.2 STATUS OF THE GCOS 7 SOLUTIONS ON DPS 7000/XTA OR NS700X OR NOVASCALE/G7XX VERSUS DPS 7000/TA................................................................................................................................. 25

4.2.1 Solutions not available ..............................................................................................................................25 4.2.2 Unchanged solutions.................................................................................................................................25 4.2.3 Modified solutions ....................................................................................................................................25 4.2.4 Solutions available on NSPR request........................................................................................................25 4.2.5 Evolution of the Interoperability Solutions...............................................................................................26

5 VISIBILITY CHANGES INTRODUCED IN GCOS 7-V11 TS 9940 .................................................. 27

6 IMPROVEMENTS INTRODUCED IN GCOS7-V11 TS 9940........................................................... 28 6.1 CHECKING OF GCOS7 SOFTWARE LICENSE VALIDITY............................................................. 28 6.2 GTWRITER SUPPORT OF 2047 DECLARED USERS...................................................................... 28 6.3 VOLSET .......................................................................................................................................... 28 6.4 VOLSAVE/VOLREST NEW PARAMETERS OFEXFSN/IFEXFSN ............................................. 28 6.5 DYNAMIC SAVE: IMPROVEMENT OF DATE MESSAGE................................................................... 29

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 3

6.6 NEW DISKS SIZES : 12, 16, 24 AND 32 GBYTES..........................................................................29

7 SOFTWARE IMPROVEMENT REQUESTS .......................................................................................30

8 PROBLEMS FIXED IN GCOS 7-V11 TS 9940 ..............................................................................31

9 DOCUMENTATION FOR GCOS 7-V11 TS 9940 ..........................................................................34

10 GCOS 7-V11 TS 9940 SYSTEM ENVIRONMENT......................................................................35 10.1 TECHNICAL STATUSES GCOS 7-V11 SUPPORTED ......................................................................35 10.2 TECHNICAL STATUSES FOR FIRMWARE AND OLTD...................................................................35 10.3 TECHNICAL STATUS OF GSF ........................................................................................................35 10.4 TECHNICAL STATUSES FOR TELECOM AND INTEROP PRODUCTS .............................................35

10.4.1 VCP7 ........................................................................................................................................................ 35 10.4.2 MainWay .................................................................................................................................................. 36 10.4.3 Interop7 media.......................................................................................................................................... 36

10.5 SOFTWARE PACKAGES..................................................................................................................36

11 ANNEX: H_NUCLEUS SERS CORRESPONDENCE..................................................................37

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 4

1 Introduction

1.1 Scope of this Customer Service Bulletin This Customer Service Bulletin introduces a new Common Technical Status of GCOS7-V11 for DPS 7000/XTA, NS700x and NovaScaleG7xx systems identified as TS 9940 UP10. During the pilot phase this TS is identified as 9939.

1.2 Presentation of the Customer Service Bulletin (CSB)

This CSB contains the following sections:

- INSTALLATION RULES OF GCOS 7-V11 TS 9940: How to update your system with GCOS 7-V11 Technical Status 9940. - REMINDER ON CHANGES INTRODUCED BY GCOS 7-V9 TS 9866 or GCOS 7-V10 and TS 9870 GCOS 7-V10 TS 9910 and GCOS 7-V10 TS 9920 and GCOS 7-V10 TS 9930. - VISIBILITY CHANGES INTRODUCED BY GCOS 7-V11 TS 9940: What needs to be changed when you upgrade your system from GCOS 7-V10 TS 9930. - NEW PRODUCTS: Brief description of the new products or main new facilities introduced by GCOS 7-V11 TS 9940. - IMPROVEMENTS IN EXISTING PRODUCTS: Brief description of the improvements included in GCOS 7-V11 TS 9940. - OBSOLETE PRODUCTS OR FUNCTIONS - DOCUMENTATION: List of documents impacted by GCOS 7-V11 TS 9940. - GCOS 7-V11 TS 9940 SYSTEM ENVIRONMENT:

Supported Technical Statuses of GCOS 7 Releases, Technical Statuses for firmware and OLTD, Technical Status of GSF, Technical Statuses for Telecom and Interop products.

Refer to GCOS 7 documentation for more details on information presented in this Customer Service Bulletin.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 5

1.3 Notice The section VISIBILITY CHANGES INTRODUCED BY GCOS 7-V11 TS 9940 presents the visibility changes compared to the Technical Status TS 9930. It must always be read to avoid problems when moving to GCOS 7-V11 TS 9940. For any visibility changes in respect of older GCOS 7 Releases, refer to BULL SUPPORT CENTER expertise.

1.4 Previous versions of the CSB

For information, the previous versions of the CSBs related to GCOS 7-V8 Release are:

CSB for GCOS 7-V8 TS 8560 UP21 Reference N° 97-019 dated December 1997 CSB for GCOS 7-V8 TS 8560 UP30 Reference N° 98-005 dated January 1998

Those related to GCOS 7-V9 Release are:

CSB for GCOS 7-V9 TS 9662 UP30 Reference N° 99-004 dated May 1999 CSB for GCOS 7-V9 TS 9764 UP20 Reference N° 99-032 dated December 1999 CSB for GCOS 7-V9 TS 9866 UP20 Reference N° 00-018 dated December 2000

Those related to GCOS 7-V10 release are: CSB for GCOS 7-V10 TS 9870 UP10 Reference N° 01-014 dated November 2001 CSB for GCOS 7-V10 TS 9910 UP10 Reference N° 02-001 dated June 2002 CSB for GCOS 7-V10 TS 9910 UP20 Reference N° 03-017 dated October 2003

CSB for GCOS 7-V10 TS 9920 UP10 Reference N° 04-009 dated March 2005 CSB for GCOS 7-V10 TS 9930 UP10 Reference N° 06-002 dated September 2006

1.5 CURRENT VERSION OF THE CSB

This related to GCOS 7-V11 release is: CSB for GCOS 7-V11 TS 9940 UP10 Reference N° 09-001 dated September 2009

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 6

2 Installation rules of GCOS 7-V11 TS 9940

GCOS 7-V11 TS 9940 supports the following DPS 7000 models

• DPS 7000/XTAxxx (DIANE)

• NS 700x (NOVASCALE)

• NOVASCALE/G7xx (NOVASCALE)

BE CAREFULL :

The TA systems DPS 7000/TAxxx (ARTEMIS2 ) and DPS 7000/TAxxxC (ARTEMIS2 ) are no more supported by GCOS 7-V11 TS 9940.

A new GCOS7 software KEY V11 is mandatory for GCOS7-V11 TS9940

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 7

2.1 First installation on XTA or NS PLATFORMS The DPS 7000/XTA or NS700x or NOVASCALE/G7xx platform is shipped with:

• WINDOWS™ 2003 Enterprise Server English version or WINDOWS™ 2008 Enterprise Server English version (from Sept 2009) with Client Access for local or LAN remote administrators and operators.

• The Virtual machine V7000 with 2 clients Access for Terminal-Service reserved for BULL usage (Remote maintenance and first RSC offer).

• Peripheral drivers and software products under WINDOWS™.

(Refer to the manual “System Operator’s Guide” Ref. 47 A2 53US Rev.09 paragraph 2.5.4 ).

• A minimal GCOS 7 Bootstrap Disk.

The customer makes the configuration of V7000 Virtual Machine with the help of BULL people (configuration of users, administrators group, operators group, access rights, GCOS 7 DISKs preparation,..). Running the GCOS 7 Bootstrap system, the customer must then: • Either restore by VOLREST his original GCOS 7-V8 or GCOS 7-V9 or GCOS7–V10 production set

followed by: an UPDATE_GCOS using the TS-media G9940 from delivered CD-ROM (don’t use an RP configuration with the minimal GCOS 7 bootstrap disk as an R-SET since a P to R LEVEL is done in that case).

WARNING : New GCOS7 software KEY V11 must be applied before reboot with the new P-SET.

• Or build a P-SET using GIUF BUILDP command with the minimal GCOS 7 bootstrap disk as an R-SET

and use of CPSITE for SITE.CATALOG, SYS.URCINIT,..

The following operations must then take place:

• Initialize GCOS 7 from the new P-SET, validate the global Marketing Identifiers Key, delete

<open7.dir>.*, SI7.*, and SYS.DCM.SYSTEM files and install the Interoperability products from the delivered CD-ROM.

• Adapt if necessary your SYSTEM startup. (Refer to manual “Interop7 User’s Guide 47 A2 91US”).

• Level the FW, GSF and DSA domains from the Minimal Bootstrap Disk (OLTD domain is no longer

used).

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 8

2.2 Updating procedure In an R/P configuration, the Technical Status is installed by UPDATE_GCOS on the P-SET. The R-SET is updated to the same patch level as the P-SET by a LEVEL operation at the beginning of the Technical Status application, and before applying the new Technical Status on the P-SET.

In a P2/P configuration, the Technical Status may be installed on any Set (running or non-running). The default is the non-running Set. The other set may be updated later using the LEVEL command of GIUF.

(Refer to the manual "GCOS 7 System Installation Configuration and Updating Guide" Ref. 47 A2 23US Rev. 05 Chapter 7).

In a PO configuration (P-Only), it is advisable to save the system disks regularly, and in any event immediately before applying a Technical Status. The minimal GCOS 7 Bootstrap Disk must be protected as it can be used to initialize GCOS 7 and recover by VOLREST the Production set after a disk destruction.

WARNING: The IUF functions BUILDP, BUILDP2, LEVEL, UPDATE_GCOS and RESTORE_SET are split into two jobs (2 XRONs). This is because they exceed the 256 steps limit allowed for a JCL member. Remember to release the outputs for both XRONs.

When the TS is installed on the running system disk, it is strongly recommended that no other job be running during the execution of UPDATE_GCOS to avoid system conflict.

Delivery of the "CLEAN" versions of updated source components requires a check of whether the patches applied on the site for these components since the last Technical Status have been included or not in the version introduced by the present TS.

A special utility called "DETECT_SITE" delivered on the Technical Status media CD-ROM must be run before applying the Technical Status itself.

DETECT_SITE uses a reference list to check if the site patches have been cleaned in the new TS and produces a list of them (LIST-1).

For patches that have not been cleaned, "DETECT_SITE" searches in a correspondence list the appropriate patch to correct the problem under the new version, and puts it in a subfile from the PATCH-MEDIA; the content of this subfile will be applied later on by UPDATE_GCOS on the new TS.

DETECT_SITE also outputs this subfile patches number as LIST-2.

If it does not find a corresponding patch, it produces a list (LIST-3). However some H_NUCLEUS site patches are listed in LIST-3 while already cleaned (it is due to internal nucleus software unit in producer data base not handled by DETECT_SITE). In the Annex are listed, by Technical Status, the corresponding nucleus site patches. A blank cell means that the SER is included (in source or as a Reference or Interim SER) in Technical Status delivery.

You must ask your Bull Support Center for the other missing patches specified in LIST-3.

(See below for running "DETECT_SITE").

The contents of the PATCH-MEDIA are periodically updated, therefore it is advisable to use the most recent version before applying the GCOS 7-V11 Technical Status. Ask your Bull Support Center to provide it.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 9

Bull S.A.S.'s responsibility cannot be involved in case of regression resulting from non-execution of the job DETECT_SITE.

You are also advised to contact your Bull Support Center before installation to check if any additional

corrections have to be applied on the new Technical Status. This is to insure correct behaviour.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 10

2.2.1 Delivery of Technical Status and Patch-media on CD-ROM for XTA or NS-SYSTEMs

FUNCTIONALITY BROUGHT BY TECHNICAL STATUS 9920 After installing the GCOS 7 TECHNICAL STATUS from the CD-ROM the GIUF functions UPDATE_GCOS and DETECT_SITE can be launched from disk . Prerequisite : INTEROP7 ID240 or upper.

Carefully read the ReadMe_Install_updg_components.txt on the CD-ROM containing the GCOS 7 Technical Status. 1. Check that FTP servers are started on Windows and GCOS 7.

Launch a Windows “command prompt” session. Change the current directory for the CD-ROM directory. Issue the following command: Install_GCOS_TECHNICAL_STATUS.

2. Log on to IOF as a user of the SYSADMIN project

3. Run the command:

S: EJ BFGIUF_MS LIB=SYS.IUF

4. (optional and only if you have received the Patch-media on CD-ROM)

Read the ReadMe_Install_detect_site_tsu_components.txt Under Windows, execute: Install_DETECT_SITE_TSU

5. Log off, then reconnect to IOF as a user of the sysadmin project to have the new GIUF domain available

6. Start GIUF: S: GIUF

7. Run DETECT_SITE: G: {DETECT_SITE|DTST } INVOL1=G9940:MS [INVOL2=DTxxx:MS] DISPLAY=1;

8. Then run UPDATE_GCOS: G: {UPDATE_GCOS|UPDG} INVOL=G9940:MS [OUTSET={P/R/P2};

Temporary space is necessary on resident disks during execution of DETECT_SITE (150000 blocks)

and UPDATE_GCOS (1200000 blocks).

Paragraph 2.2.3 to 2.2.11 are always available for XTA or NS systems. Read them before starting the Technical Status Installation.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 11

2.2.2 Running the DETECT_SITE Utility

If you have not received the "PATCH-MEDIA" with your "TS-MEDIA", you must still run DETECT_SITE, but without entering the INVOL2 information.

All SITE patches that have not been cleaned in the new TS will appear in the LIST-3 produced by DETECT_SITE. Please contact your Bull Support Center in order to get the missing patches.

1. Log on to IOF as a user of the SYSADMIN project,

2. Start GIUF:

S: GIUF

3. Then run DETECT_SITE:

using CD-ROM :

G: {DETECT_SITE | DTST} INVOL1=G9940:MS [INVOL2=DTxxx:MS] [DISPLAY=1]

(if DISPLAY=1 is specified a report is produced on the submitting console)

Carefully read paragraphs 2.2.3 to 2.2.11 before starting the Technical Status installation.

2.2.3 Prerequisites

Make sure that a new GCOS7 software KEY V11 has been provided before installing GCOS 7-V11 TS 9940.

2.2.4 Installing the Technical Status

1. Log on to IOF as a user of the SYSADMIN project. 2. Check that H_SCANNER, H_EXECUTE and H_WRITER modules are preinitialized. If these

modules are not preinitialized, issue MDC PLM=H_SCANNER, MDC PLM=H_EXECUTE and MDC PLM = H_WRITER commands at the main console.

3. The preinitialization of these modules is mandatory to insure a good execution and the edition of the result of the UPDATE_GCOS command.

4. Check that temporary space is available either on resident disks if site VOLSET is not active or on disks declared as containing temporary files if site VOLSET is active. The size of the temporary space required is about 8 Mbytes.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 12

Then enter:

S: GIUF

5. Enter the UPDATE_GCOS function of GIUF (alias UPDG) at the G: prompt

Using CD-ROM:

G: UPDG INVOL=G9940:MS [OUTSET={P|R|P2}];

WARNING - WARNING - WARNING - WARNING - WARNING - WARNING - WARNING ******************************************************************************************************* After GCOS7 update, it is imperative to validate the new GCOS7 software key V11 on the system before terminating the current GCOS 7 session otherwise the system will not be able to restart.

2.2.5 Checking Transferred Patches

Carefully read the OUTPUT of the first job of UPDATE_GCOS of GCOS 7-V11 TS 9940 installation to find any patches with the following message in "LIST OF NOT TRANSFERRED SER'S":

"PATCH HAS SYMB V U I=REF, REAPPLY SOURCE PATCH WITH INSST"

If such patches exist, they must be manually re-applied by means of the GIUF PATCH_HLMLIB function (alias PATLM).

2.2.6 INIT of the System

After installation of the GCOS 7-V11 TS 9940, an INIT of the system is mandatory. Make sure that your GCOS 7 software validation key has been validated followed by system CONFIG completion before re-initializing your system.

2.2.7 Restarting the System

1. In order to validate the new Technical Status, it is mandatory to perform an ISL with:

RESTORE,RESTART(CLEAN),[NSYSSTUP]

NSYSSTUP option must be used if any telecommunication activity is generated in system startup (like SOW spool launching).

2. Answer N (no) to the NG03 question:

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 13

"NG03 DO YOU WANT TO LOAD PREVIOUSLY SAVED TELECOMMUNICATION CONFIGURATIONS ? (Y,N), DEFAULT=Y"

3. At question OU16:

"SYS.OUT RECOVER?"

the answer can be Y (Yes) or N (No).

4. After GCOS READY, it is mandatory to execute a CRNETGEN (basic and incremental).

5. If the RESTORE of the system has been executed with NSYSSTUP option, it is necessary to run the STARTUP system manually.

As the CLEAN part of the SYSTEM startup is executed when the value of the third switch is equal to 1, set the value of this switch to 1 by the command:

SET_SWITCH SWITCH2=1

and execute the command:

AI SYSTEM LIB=SITE.STARTUP

2.2.8 SECUR’ACCESS

After GCOS 7-V11 TS 9940 installation, you must do the following:

1. When using version V3.3 (or later) of SECUR'ACCESS, copy the members SA7VL and SA7_MBXNAME from the library SA7.LIV.SL to the library SYS.HSLLIB.

S: LMN SL LIB=SYS.HSLLIB; C: IL1 SA7.LIV.SL; C: MOVE SA7VL INLIB1; C: MOVE SA7_MBXNAME INLIB1, INFORM=SARF, OUTFORM=SARF; C: QUIT;

2. Update the SM library H_SM_DUAL using the JCL SA7-SMDUAL in the SL library SA7.LIV.SL:

S: EJ SA7-SMDUAL,,SA7.LIV.SL

3. Update the library SYS.HBINLIB by transferring the security remote loading modules from SA7.LIV.BIN:

S: LMN BIN SYS.HBINLIB; C: IL1 SA7.LIV.BIN; C: MV *SECUR* IL1; C: QUIT; (To be performed only in case of Smartcards usage)

4. Apply the specific corrections necessary to SECUR’ACCESS (contact your Bull Support Center).

5. Perform an ISL RESTORE session of your system.

2.2.9 RDDF 7-V2

GCOS 7-V11 TS 9940 is delivered with RDDF7 V2.3 which supports ORACLE Version 7.3.4.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 14

2.2.10 Restarting Production

Before restarting production carefully read the section VISIBILITY CHANGES INTRODUCED BY GCOS 7-V11 TS 9940.

1. TDS/GTWriter

After the application of any Technical Status, you must regenerate all your TDSs (TP7GEN) and GTWriter (TWGEN) before using them.

2. MML

After the application of any Technical Status, you must regenerate your MML application (MMLGEN) before using it (Note that in text mode MML uses ASCII translation tables ).

3. TWCOMM

When restarting TWCOMM for the first time after the TS application, the value "CLEAN" must be used for the first parameter.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 15

2.3 Technical Status Documentation The documentation which describes the contents of the Technical Status is located on the cd-rom. You can print the documentation, called IUF_DOCTS.DOC, in a text format (Notepad or Wordpad).

2.4 Disk Space Occupancy

The minimum disk space occupancy on FSA volumes found after an INSTALL_ALL of the GCOS, DSA, FW, OLTD and GSF Domains is the same as in GCOS 7-V10 TS 9930 and is approximately equal to 900 Mbytes.

2.5 Identification of GCOS 7-V11 TS 9940 in the banners

A given Technical Status may have several update levels. The level of update is referred as UPxx. This level is displayed in the different banners of GCOS 7-V11 TS 9940. The banner printed out in the SYSOUT is as follows:

KA15 V11 9940 SM: UP10 LM:9940 FW: D621 90029001 PR/H136 The banner received on an IOF connection to GCOS 7-V11 TS 9940 looks like:

>>>08:35 IOF-KA15 V11 SYS: 9940 SM: UP10 LM: 9940 FW: D621

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 16

3 Reminder on changes introduced from GCOS 7-V9 TS 9866 to GCOS 7-V10 TS 9930, included in GCOS 7-V11 TS 9940

The visibility changes presented in this section include the changes that you must take care of when installing the new technical status so that the current running operations are not disrupted. It does not cover neither the new functions nor the modifications in the different output displays.

3.1 Visibility changes introduced by GCOS 7-V9 TS 9866 or GCOS 7-V10 TS 9870

3.1.1 GCL COMMAND MDLD CLASSLIST PARAMETER

In the manual SYSTEM OPERATOR’S GUIDE 47 A2 53US Rev.07 page 8-46 the PARAMETER CLASSLIST (or CLASS) syntax is changed to: SYNTAX [ { CLASSLIST} {aa [-aa] }] [ { } = { }] [ {CLASS } {aa }] PARAMETER The default value CLASSLIST=* is no more assumed, the USER must specify the JOB class or classes whose attributes he wants to modify. This change prevents from modifying all classes by mistake.

3.1.2 OCS DRIVER LOAD MODULES

The following load_modules have been renamed: H_NCCD7 is renamed H_VCPD7 H_NCC_EDTRACE is renamed H_VCP_EDTRACE H_VERIFYNCC is renamed H_VCP_VERIFY The new names appear on some display commands (as DISPLAY_JOB, DISPLAY_CONFIGURATION), and these new names have to be used in the GCL command MODIFY_CONFIGURATION in the keywords PLM or CLM.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 17

3.2 Improvements introduced in GCOS 7-V9 TS 9866 or GCOS 7-V10 TS

9870

3.2.1 NEW KEYWORD ERASE OF GPL PRIMITIVE H_DEALLOC

The GPL primitive H_DEALLOC new keyword ERASE allows to reset to binary ZEROes the file disk space for security reasons (if this disk space is allocated to a new file it becomes not possible to display (by MAINTAIN_FILE,,) previous recorded DATA) .

3.2.2 Standard GPL primitives

3.2.2.1 H_TRTIME

This standard GPL primitive has been delivered to fix RC= SNDARERR bug since GCOS 7-V7 TS 7560. This version is also immediately available on request to BULL support center for other GCOS 7 Technical Statuses.

3.2.2.2 H_BEGDEF

This standard GPL primitive is delivered for suppression of the release name at the beginning of the macro.

3.2.3 TDS – TCP/IP option DATACONVERT

A new option is given to manage ASCII – EBCDIC conversions in TDS TCP/IP. It allows to specify at connection level whether the user’s data must be converted or not.

3.2.4 TDS - TCP/IP FUNCTION BREAK

* BREAK functionality: A client application can send a BREAK to TDS by calling tpsend with the « H_BREAK » message. If TDS get the turn in less than 2 minutes the BREAK transaction is started and the current transaction is interrupted. If not the TDS-TCP/IP client is disconnected.

3.2.5 TDS – TCP/IP API for 3-tiers architecture with NT server

This improvement provides a 3-tiers architecture for TDS TCP/IP API with an intermediate NT server. It concerns only the DLL TDS TCP/IP .

3.2.6 Improve TDS maximum declared transactions number

A TDS generation may declare up to 3000 transactions.

3.2.7 GCOS 7 GTWRITER support of 15000 declared terminals

The maximum number of pools was limited by the constraint that the total of pools and terminals declared may not exceed 3000 (Each pool must contain at least 2 and not more than 16 terminals). This limit for GTWRITER generation is increased to 15000 allowing to declare in GTWRITER generation several time the same physical printer (with different access path,..)

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 18

3.3 Visibility changes introduced in GCOS 7-V10 TS 9910

3.3.1 TDS TRACE PRINT

All unsuccessful or abnormally completed UFAS verbs are now traced.

3.3.2 ARM: improvement in messages

Messages SH19 and RS04 are modified to specify the resource the step is waiting for: SH19 : WAIT FOR MPL IN DIMENSION xxxx RS04 : RESOURCES NOT AVAILABLE NOW : MPL IN DIMENSION xxxx where MPL stands for multiprogramming Level.

3.4 Improvements introduced in GCOS7-V10 TS 9910

3.4.1 TDS

3.4.1.1 Commands MDTMOT AND SNDTU: increase size of message

For these two master commands, the maximum size of the message is increased to 250 characters instead of 46 characters previously.

3.4.1.2 Watchdog

A new clause “WATCHTIME” is added in the TDS SECTION. It allows to specify the time for the network to answer to TDS before the session is disconnected by TIMEOUT. This clause is a generalisation of the WATCH-TIME field of the TDS-STORAGE and applies with the same rules.

3.4.1.3 Support of 3000 users connected through tcp/ip

On XTA or NS platform from Interop7 release ID230, 3000 users can be connected to one or several TDS applications of a GCOS 7 system through tcp/ip instead of 1000 previously.

3.4.1.4 Multiple user

A new clause “MULTIPLE-USERS-prefix” is added in the TDS SECTION. It allows to connect the same user several times to the TDS and thus to create user’s pools that can be used, for example, from an Application Server. Ex: clause USE MULTIPLE-USERS-MPX in TDS SECTION. The user “JOHNMPX is added in the catalog. Up to 999 users can connect to this TDS, using JOHN* as

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 19

name. They will be known in TDS as JOHN001, JOHN002,...,JOHN999.

3.4.2 Extension of proxy access rights

PROXY access rights are extended to utility MODIFY_FILE (FILMODIF in JCL).

3.4.3 NEW LM H_VOLCHECK

This utility is launched by the JCL H_VOLCHECK of the SYS.HSLLIB. It allows to check and/or repair an FBO volume whose VTOC has been damaged.

3.4.4 Copy files for LIST_VOLUME or LIST_FILE OUTFILE contents

A set of Cobol copy files are delivered in SYS.HSLLIB to describe the content of the records produced by LIST_VOLUME and LIST_FILE commands in an outfile.

3.4.5 GTWRITER

3.4.5.1 New parameter BARCODE in FORM statement

This parameter specifies that on each line, all trailing spaces are replaced by one space.

3.4.5.2 New parameter USER for DPRINT command

This parameter, that already exists in the OCL command TWR, specifies the owner of the report to be printed.

3.4.5.3 Size of report name on 8 characters

By compatibility with output-writer the name of the reports can be specified with 8 characters.

3.4.6 Dynamic save: improvement of error message

In the JOR of DYNSAVE when option LINKDSET is used, when trying to save a file already being saved, the rank of this file in the list will be added in message DU95. This message becomes: TWO DYNAMIC SAVES ON THE SAME FILE (nnnnn) where nnnnn is the rank of the file in the list.

3.4.7 COBOL: new option NCKUKFIL to compile a tpr

The NCKUKFIL parameter suppresses the checking of STDS files in the TPR prolog. It requests the compiler not to emit, in the prolog of a program which contains one (or several) FD clause(s), some usual code which would cause the program to abort at run time under TDS if a file is not described in STDS subfile. There is no checking about such unknown files: they may be absent from the STDS subfile, and from the JCL of the TDS.

3.4.8 IOF: clean user’s mailbox

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 20

The JCL command CLEANMBX allows to delete all messages of an IOF mailbox user. The user must specify the name of the user whose IOF mailbox is to be deleted. EJR CLEANMBX LIB=SYS.HSLLIB VALUES=(user_id) Only a MAIN operator or a SYSADMIN user can delete the IOF mailbox of an other user. Other users can only delete their own mailbox.

The user whose IOF mailbox is to be deleted must not be connected to the IOF application. This facility can be very useful when users connected to a TDS application launch a very large number of batch jobs that generate many messages toward theirs IOF mailboxes. These mailboxes can be deleted by launching CLEANMBX by mean of a call SUBJOB.

3.4.9 Config: new parameter lines for jobclass statement

The new parameter LINES in Config statements JOBCLASS and JBCLASS2 specifies a 8-digit decimal number, indicating the default maximum number of records that may be written in SYSOUT file for job steps running in the defined job class. It is possible to override this default value, at step execution time, by using the LINES parameter in the JCL statement STEP, or in the GCL command EXEC_PG. The default value (99999999) means that there is no default limit on number of print records. No limit can be set for service job classes (R-Z and RA-ZZ).

3.4.10 C LANGUAGE: improve MALLOC and FREE.

Inside a multi-process process-group, memory obtained via malloc (or calloc or realloc) in a process can be freed in another process.

3.4.11 Access to user’s label from cobol

A new COBOL call “H_QL_UGETLAB” allows reading user’s label of a member of library. In addition, a new COBOL copy file is delivered that describes the user’s label created by Queued Writers.

3.4.12 RFC1006

RFC1006 (transport of DSA sessions on TCP/IP) is now included as a standard function.

3.5 VISIBILITY CHANGES INTRODUCED IN GCOS 7-V10 TS 9920

3.5.1 GTWRITER

CSETTYPE of GTWRITER terminals is now retrieved from H_TERM member of the SYS.HSLLIB. If the value of the CSETTYPE parameter, defined in the H_TERM member, is not suitable for the customer, it has to be changed in the H_TERM subfile by the customer himself. example: For PRT1220 (DSAMODEL=205C) , the default CSETTYPE in H_TERM is 1.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 21

If the customer wants to use the PRT1220 with the CSETTYPE = 2, he has to replace CSETTYPE=1 by CSETTYPE=2 in the H_TERM of the SYS.HSLLIB for the PRT1220 model. Warning: The modification of the H_TERM implies new telecom generation using the CREATE_NETGEN (NG) with the parameter CRTERM. (Refer to documentation 47 A2 93UC Network Generation User's Guide)

3.6 IMPROVEMENTS INTRODUCED IN GCOS7-V10 TS 9920

3.6.1 TDS

Master TDS command Display_Tds_Socket (DTDSS) has been modified to display a list of TDS-TCPIP correspondents with their IP address and their peer port. Support in TDS of the MULTI_SYS_TW_OUT functionality.

3.6.2 GTWRITER

New parameter MULTI_SYS_TW_OUT in the generation, allowing to use different SYS.TW.OUT(i) file for each TDS. This enhancement allows to spread I/Os among several disks.

3.6.3 DJP

New GPL primitive H_DJRFLST and declarative H_DCDJRFLST to get in a program the list of all known distributed job processing requests (same as result of ‘DDJP ALL’ command).

3.6.4 Job Management

New GPL primitives H_HJFORBIDDEN and H_HJALLOWED to forbid then allow again the suspension of the running job.

3.6.5 GIUF

Delivery of Technical Status GCOS 7 and Patch-media on CD-ROM, only for XTA or NS-SYSTEMs, allowing to execute the functions UPDATE_GCOS and DETECT_SITE from disk.

3.6.6 MAINTAIN LIBRARY SM

Modify listing of LS sm_name DETAILED command of MNLIB SM to list for each LKU STN, STE and size of private data and the number of working segments required during loading of SM. When the limit of this number is reached (255), the following message is displayed: ”**WARNING: TOO MANY WORKING SEGMENTS (>255) FOR LOADING SM.”

3.7 VISIBILITY CHANGES INTRODUCED IN GCOS 7-V10 TS 9930

3.7.1 ARM

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 22

Alignement of results of DDIM command OPTION=RCS and RON has been modified to take into account an I/O frequency value up to 9999 (column IO/S)

3.7.2 H_VOLCHECK

The JCL H_VOLCHECK is reserved to BULL support and must be used with care to avoid system problem like pseudo-deadlock. Do not launch two H_VOLCHECK in parallel but one by one. The library (LIB parameter) using to receive the report of H_VOLCHECK must not be allocated on the media which is checked.

3.8 IMPROVEMENTS INTRODUCED IN GCOS7-V10 TS 9930

3.8.1 TDS

Maximum number of families of virtual correspondents allowed in TDS generation is increased from 5 to 20.

3.8.2 DP_SAVE

New parameter FTP in EXECUTE_DP_SAVE command, allowing to transfer the results of a DP_SAVE by FTP. Warning: this enhancement is only available on DPS7000/XTA or NS700x or NovaScale/G7xx systems.

3.8.3 SWLOG

New JCLs “START_SWLOG” and “STOP_SWLOG” allowing to increase the capacity of system trace sent to SYS.SWLOG file.

3.8.4 WRITER QUEUED

New LOAD MODULE H_SENDGTW allowing to send automatically OUTPUTs from SYS.OUT to a GTWRITER Terminal, using JCL_CONTROL functionality of WRITER QUEUED.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 23

4 Visibility changes introduced by DPS 7000/XTA or NS700x or NovaScale/G7xx

The visibility changes presented in this section include the changes that you must take care of when installing the new technical status so that the current running operations are not disrupted. It does not cover neither the new functions nor the modifications in the different output displays.

4.1 Customer DATA MIGRATION All the existing data on tape or cartridge are accessible and compatible. Data on disks must be transferred to XTA or NS platform using save/restore or telecom facilities. Most of the user’s applications under GCOS 7 can run “AS IS” without any modifications. There are some differences for applications using Interop7 facilities (see § 4.2). There is a BULL service defined to help customers for their data migration (call your BULL Service Center).

4.1.1 Compatibility rules between former DPS 7000 and DPS 7000/XTA or NS 700x or NovaScale/G7xx platforms

Disk Data format is not compatible between a disk subsystem connected to a former DPS 7000 platform and a disk subsystem connected to a DPS 7000/XTA or NS platform, therefore it is not possible to share a GCOS disk volume between a former DPS 7000 platform and a DPS 7000/XTA or NS platform. To re-use or exchange data between a former DPS 7000 platform and a DPS 7000/XTA or NS platform, use either tape or cartridge media or telecommunication facilities.

4.1.2 User DATA BASE Evolution

Production must have been stopped when data base files are saved, in order to preserve data/index consistency.

IDS2 Data bases

IDS2 files can be saved/restored using either GCOS 7 VOLSAVE/VOLREST option REORG or GCOS 7 FILSAVE/FILREST utilities.

Large UFAS Files

UFAS files can be saved/restored using either GCOS 7 VOLSAVE/VOLREST option REORG or GCOS 7 FILSAVE/FILREST utilities.

ORACLE Data bases

If the ORACLE data base is located on DPS 7000 GCOS 7, it can be saved/restored using either GCOS 7 VOLSAVE/VOLREST option REORG or GCOS 7 FILSAVE/FILREST utilities. Customer can also take benefit of the migration toward a DPS 7000/XTA or NS to reorganize or migrate the Oracle data base. This can be done using EXPORT / IMPORT procedures of the Oracle software. Refer to Oracle documentation.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 24

4.1.3 GCOS 7 Disk File

A GCOS 7 volume is mapped onto a DPS 7000/XTA or NS700x or NovaScale/G7xx Windows™ file (in NTFS format). After the file has been created, the contents of the corresponding GCOS 7 volume have to be restored using standard GCOS 7 utilities (VOLREST option REORG / FILREST). The effective sizes of the XTA or NS GCOS volumes are: 20971 * 100K for a XTA 2 GB file

41943 * 100K for a XTA 4 GB file

83886 * 100K for a XTA 8 GB file

94371 * 100K for a XTA 9 GB file (requires a disk with a minimum 18 GB physical size)

Important: In case of reconnection of 9GB physical size disk, sizes listed above show that a 9GB disk that is more than 95% full can not be restored on an DPS 7000/XTA or NS700x or NovaScale/G7xx 8GB file. The disk must be reorganized before it can be migrated.

4.1.4 Migration of System files

SITE.CATALOG, SYS.URCINIT, SITE.HELP, SITE.STARTUP, SITE.QUOTA, SITE.MFT must be migrated before the data migration operations start. A special JCL called “UP_URCINIT” in SYS.HSLLIB can be used to reinsert in the User’s restored SYS.URCINIT the GCOS 7-V10 tables delivered for PR900 family printer with EURO sign support.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 25

4.2 Status of the GCOS 7 solutions on DPS 7000/XTA or NS700x or NovaScale/G7xx versus DPS 7000/TA

4.2.1 Solutions not available

BI-SYSTEMS EXTENDED PROCESSORS BOOSTER FUNCTION AFFINITY under OPEN7 DDA and DDW DPF7 DW7 EB7 EWEB7 replaced by GWEB GMP7-AG Mirror Disks (replaced by RAID1 hardware technology) NATSTAR7 NFS7 XFORMS

4.2.2 Unchanged solutions

DA7 ESP7 HooXGCOS 7 Connector HooXJMS7 HooXWeb Services JESP7 JTDS JUFAS ORACLE7 SA7 SNMP7 SOCKG7 SQL*XT TDS-WEB TNVIP/Viplet

4.2.3 Modified solutions

CLX CNDSA FTP7 OPENGTW SUBUX

4.2.4 Solutions available on NSPR request

GXRPC FLOWBUS SA7-ACCESS MASTER

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 26

4.2.5 Evolution of the Interoperability Solutions

Gateways which where previously on OPEN7 have been ported on Windows™. All other gateways on GCOS 7, on UNIX, on MainWay or on PC are unchanged. By the fact, as some solutions (such as Telnet Server7) are no longer required on DPS 7000/XTA or NS700x or NovaScale/G7xx, only three gateways remain on Windows™: • OpenGTW for Print,

• FTP7,

• NT7GW for ESP7, DA7, Java,

Interop7 solutions for DPS 7000/XTA or NS700x or NovaScale/G7xx are the continuation of existing solutions on DPS 7000/TA. There is no functional change for the user (and especially no modification in the TDS applications). Only administrative tasks may be required: • Install / configure the gateways,

• Regenerate TDS if you use the TCP/IP access of TDS for ESP, DA7, or Java to TDS solutions,

• Recode the OpenGTW scripts,

• Replace NFS7 UFAS access (if any) by the JUFAS access,

• Replace GXTI access to TCP/IP by SOCKG7 access to TCP/IP, if any,

• Modify the FTP scripts when they use the former #Gfile syntax,

• Transfer OPEN7 scripts on an external UNIX server,

• Replace user developments on Open7 (if any) by equivalent ones on WindowsTM.

• SUBUX: add system name in command and rewrite remote scripts.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 27

5 Visibility changes introduced in GCOS 7-V11 TS 9940

None

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 28

6 Improvements introduced in GCOS7-V11 TS 9940

6.1 CHECKING OF GCOS7 SOFTWARE LICENSE VALIDITY Expiration date of the GCOS7 software license is checked. Customer will be notified during 90 days before and 14 days after the expiration date of the GCOS7 software license with the following messages. The fifteenth day after the end of licence validity, the system will be stopped. From 90 days to 30 days before the expiration of GCOS7 software license date, the following warning message is sent to the Main Operator consoles every day between 12 PM to 15 PM : CS20 WARNING : GCOS7 LICENSE WILL BE EXPIRED ON : “expiration_date” During the last 30 days before the expiration of the GCOS7 software license date, the following warning message is sent to the Main Operator consoles every 3 hours : CS20 WARNING : GCOS7 LICENSE WILL BE EXPIRED ON : “expiration_date” During the 15 days after the expiration of the GCOS7 software license date, the following fatal message is sent to the Main Operator consoles every 3 hours : CS21 FATAL : GCOS7 LICENSE EXPIRED, SHUTDOWN SYSTEM ON : “shutdown_date” The fifteenth day after the expiration of the GCOS7 software license date, the following fatal message is sent to the Main Operator consoles and the system stops CS23 FATAL : GCOS7 LICENSE EXPIRED, SHUTDOWN SYSTEM After a system shutdown due to expiration of the GCOS7 software license date, the restart of the system is allowed during one hour to be able to apply the new licence. In this case the following fatal message is sent to the Main Operator consoles : CS22 FATAL : GCOS7 LICENSE EXPIRED, SHUTDOWN SYSTEM IN ONE HOUR

6.2 GTWRITER SUPPORT OF 2047 DECLARED USERS This limit for GTWRITER generation of declared users is increased to 2047.

6.3 VOLSET The maximum number of volumes for one VOLSET is increased to 128.

6.4 VOLSAVE/VOLREST new parameters OFEXFSN/IFEXFSN New parameter OFEXFSN in VOLSAVE statement allowing to specify a file sequence number (FSN) up to 9999 when OUTFILE parameter on tape/cartridge is used. New parameter IFEXFSN in VOLREST statement allowing to specify a file sequence number (FSN) up to 9999 when INFILE parameter on tape/cartridge is used.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 29

6.5 DYNAMIC SAVE: IMPROVEMENT OF DATE MESSAGE JAS date is now sent at start time of batch DYNSAVE to the submitter.

6.6 NEW DISKS SIZES : 12, 16, 24 AND 32 Gbytes New physical disk sizes : 12, 16, 24, 32 Gbytes are supported by GCOS7-V11 The effective sizes of the new disks are: 125828 * 100K for a 12 GB

167772 * 100K for a 16 GB

251658 * 100K for a 24 GB

335544 * 100K for a 32 GB The maximum number of files per disk has not be enlarged. The GCOS7 maximum size of one extent is 8 Gbytes, then the number of extents created by PREPARE_DISK utility is egal to the physical disk size modulo 8 Gbytes. i.e. : for a 32 Gbytes disk , 4 extents of 8 Gbytes each are generated with PREPARE_DISK Warning : This improvement is only available on DPS 7000/XTA, NS700x and NovaScaleG7xx systems with Technical Status 9940 GCOS7-V11 and V7000 version V6.2.1 and upper.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 30

7 Software improvement requests The following table gives the list of the GCOS 7 improvement STARs and of the European User’s Association requests which have been integrated in this Technical Status:

PES Summary Apria (June 2008) Improve capacity of GCOS7 disks (§ 6.6)

Improvement STARs Summary 013008 Improve maximum of declared users in GTWriter generation(§ 6.2) 013715 Improve number of volumes per VOLSET(§ 6.3) 014095 New parameters IFEXFSN/OFEXFSN for VOLREST/VOLSAVE(§ 6.4) 013500 Improve to send JAS date of batch DYNSAVE on submitter console(§ 6.5)

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 31

8 Problems fixed in GCOS 7-V11 TS 9940

ARM

014056 : ERROR WITH EXDIR: DISPLAY_ERROR_LOG SELECT=SYSERR;

CMN 013364 : ABORT EXCEPTION 11-02 SUBSCRIPT OUT OF ARRAY RANGE @ ADDRESS F.A7.7D60

COBOL 012453 : DISPLAY UPON CONSOLE NOT OK

DFASG 014321 : TAPE MEDIA 9004 RESERVED BY X9723 ORACLE JOB WRONGFULLY

DFPRE

013886 : ABORT GSORT RC=4BD10481->DFPRE 17,IOFAIL

DFSRD

013719 : ABORT VOLSAVE WITH DSMGT 42 FLABUNKUN 4B2A100F ON TEMPORARY FILE

DJP 013136 : DEADLOCK SYSTEM : JOBS KEEPS IN STATUS.MANY PROCESSES ARE WAITING AT

A.80.044C IN H_RB_JGSTION/0+44C ON H_SDT_SEM 013234 : ABNORMAL START OF JOBS AFTER TS COMMAND OF V7000 AND REBOOT OF GCOS

WITH WARM RESTART 014032 : LOAD MODULE H_FTF ABORTED @ B.10.48E0 WITH DIFFERENT EXCEPTIONS TYPE

0E-01 AND 07-00

DSMGT 011960 : QT02 -> QVS30 BUSY ON MNQ/LSP COMMAND 015987 : CRASH CALL TO PANIC FROM J=88 P=00 CODE=1C0B PARAMETERS 1C07000B 88008800

00004E20 GAC

016096 : AFTER ABORT WITH RC=B3CF0D00->XAC 15,DEADLOCK & STEP REPEATED

LOOP @ E.25.1FFC - TJ NOT OK

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 32

JTRA

012536 : ABORT SORT WITH DFASG 3, CONFLICT RC= 4B830460 012459 : GARBAGE IN REPORT OF EXECUTE COMMAND

JOB 015571 : SYSTEM STARTUP ABORTED WITH MESSAGE ***GCL ERROR: UNABLE TO PERFORM RC=1B2B1205->JOBM 43,MSGOV.

LBMNC 012533 : Under LIBMAINT SM, a LKU of a SM can be deleted even if another SM name has been specified in the DELETE command.

LFA

014777 : ERRONEOUS DISPLAY OF VALUES OF VC ON LFA COMMAND 015214 : ERRONEOUS DISPLAY OF DURATION OF CHARACTER VOLUME TRAFIC WITH COMMAND

LFA OF VC RST

014368 : NO MORE CONNEXIONS POSSIBLE ON THE 2 OCS EA01 EA11; RELOAD MUST BE DONE

SCHDL

012727 : BAD DISPLAY IN THE RESULT OF THE COMMAND DS <<SBR RON>> DETAILED THE VALUE BS= IS NEGATIVE

SBR

011992 : SBR ANALYSIS ABORT RC=25E91800->SBR 41,PARAMERR OK_MISS1_ALL__ # LABEL NOT DEFINED

SYSIN

013421 : CRASH CALL TO PANIC FROM J=2D P=02 CODE=4C64 PARAMETERS:4C450064 2D020000 3D1A0000 AFTER A LOOP OF ABORTS LEADING TO LACK of SEGMENTS RC=20581223->VMM 88,ENTRYOV

TD

015345 : ABORT H_DBUTILITY EX01. EXCEPTION 11-02 AT F.41.181A .( H_TD_IWK )

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 33

TP7

012736 : MU59 TDS ABORT : INTERNAL ERROR IN VCAM INTERFACE. ICC @ E.49.D0D4 E.C1.19FC E.33.01AE VCAM STATUS (HEXA) = 94 RC=84841853->VCAM 4,ARGERR 012892 : SBR DO NOT GIVE REPONSE TIME WITH TDS USING TCP/IP 013895 : TDS ABORT SWAP INCONSYSTENCY DETECTED ON COMMAND TKMB FORCE (TDS HA) 013939 : DEADLOCK WHEN TDS IS STARTED AT E.C1.C526 AND E.BD.DB20 014025 : SDM TERMINATED AFTER PX13 OUT & WRONG RECOVERY OF TDS FILES LEADING TO FLNAV 014385 : TDS ABORT DURING A SPAWN ON AN UNKNOWN CORRESPONDENT : "MU63. ERROR DETECTED WHILE ACCESSING TDS SWAP FILE. RC=00000000->DONE".

TSEQL

012761 : LDFST ABORTED WITH EXCEPTION @ ADR C.4C.006A CLASS=06 TYPE=00

TW 011778 : ABORT H_TWRITER EX01. EXCEPTION 06-00: ACCESS OUT OF SEGMENT BOUNDS

(SEGMENT 8.31) IN TASK MAIN.0 AT ADDRESS 8.33.614E 015523 : DEADLOCK : NO POSSIBILITY TO START A JOB ERROR MESSAGE : H_TN_ETINVOK, UNSUCCESSFUL ASSIGN LIBRARY RC=1C1E1223->TASKM 30,ENTRYOV

VCAM 015803 : CALL TO PANIC FROM J=01 P=05 CODE=8481 PARAMETERS:84803401 01050400 191404C6

VCP7 011564 : SYSER VCP7 ERROR 0012 THREAD_STREAM_FAILED 012270 : ERROR WHEN LAUNCHING OCS : ESTABLISHMENT OF TRANSPORT ENDPOINT FAILED GXTI T_OPEN ERRNO: 40

XBUP 011930 : THE PURSUIT IS RUNNING, BUT DOESN.T INSERT THE MODIFIED DATA INTO THE

CUSTOMER FILES 013342 : DUMPJRNL ABORT EXCP 06-00 OUT OF SEGMENT BOUND AT ADDR. F.CC.13D8 015457: RDDF ABORT H_WIND_MEMO ERROR DEBCODE=760002 RC=144C1853->XBUP 76,ARGERR

XUFAS

015743 : EFN WRONGLY DISPLAYED ON MESSAGE :

WARNING *** INCIDENT DETECTED FOR THE FILE:EFN =

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 34

9 Documentation for GCOS 7-V11 TS 9940

The following manuals have been updated to reflect the changes brought by GCOS 7-V11 TS 9940:

TITLE Reference

GTWRITER User’s Guide ............................................................47 A2 55UU Rev. 10 Data Management Utilities User’s Guide .....................................47 A2 34UF Rev. 06 Storage Management Administrator’s Guide ...............................47 A2 36UF Rev. 03 GCOS7 Messages and Return Codes Directory..........................47 A2 10UJ Rev. 12 GCOS7 Console Message Directory ...........................................47 A2 61UU Rev. 10

Note that these manuals ARE NOT part of the Technical Status kit. If you have a subscription, you will get them through the normal subscription conditions. They are also delivered when the corresponding products are ordered.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 35

10 GCOS 7-V11 TS 9940 system environment

10.1 Technical statuses GCOS 7-V11 supported

TS 9940 UP10 no more supported on all TA models

10.2 Technical statuses for firmware and OLTD The FIRMWARE and OLTD Technical Statuses running on a system disk can be displayed under IOF (not the main operator), using the following commands:

S: GIUF COMMAND=DISPLAY_STATUS

The values given in the table below are the minimum Technical Statuses required by GCOS 7-V11 TS 9940.

DPS 7000 MODELS FW OLTD

DPS 7000/XTAxxx or NS700x or NovaScaleG7xx

D621 None

10.3 Technical status of GSF The value given in the table below is the Technical Status recommended by GCOS 7-V9 TS 9866 UP20 and GCOS 7-V10. There are patches for Software Telecontrol version running on DPS7000/XTA or NS700x or NovaScale/G7xx, a level from the Minimal Bootstrap Disk is necessary if GSF 122 is installed from tape media .The GSF Technical Status running on a system disk can be displayed under IOF, using the following command: S: GIUF COMMAND=DISPLAY_STATUS

DPS 7000 MODELS GCOS 7-V11

GSF Any model 122

10.4 Technical Statuses for Telecom and Interop products

10.4.1 VCP7

The various telecommunication Technical Statuses running on a system disk can be displayed under IOF (not the main operator), using the following command: S: DIUF LIST

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 36

The minimum Technical Status recommended for VCP7 is listed below (for standard marketing configurations).

DPS 7000 MODELS Technical status

VCP7 DPS 7000/XTA NS700x NovaScale/G7xx D000

.

10.4.2 MainWay

The minimum Technical Status recommended for DNS-E is “V3U3” (Mandatory for TDS-Web support).

10.4.3 Interop7 media.

DPS 7000/XTA or NS700x or NovaScale/G7xx platforms: ID430, ID440

10.5 Software packages Check with the providing Software Houses: • if the versions of the software packages that you are using need to be updated in order to run correctly

with GCOS 7-V11 TS 9940 Release • and, if new keys need to be validated because the CPU number has changed.

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 37

11 Annex: H_NUCLEUS SERs correspondence

In the following table, updated September 2009, each column is associated to a GCOS 7 Technical Status, each line gives the corresponding SERs. Cleaned means that the SER is included in source.

TS 9866 UP20 TS 9870 UP20 TS 9910 UP20 TS 9920 UP10 TS 9930 UP10

P9226.01 P9226.01 CLEANED P9551.01 P9551.01 CLEANED P9731.01 P9731.01 CLEANED P9893.01 P9893.01 CLEANED P9929.01 P9929.01 CLEANED Q0474.02 Q0474.02 CLEANED Q0650.01 Q0650.01 CLEANED Q0809.01 Q0809.01 DELETED Q4077.01 Q4077.01 CLEANED Q1445.01 Q1445.01 Q1445.01 CLEANED

Q1715.02 CLEANED Q2075.01 Q2075.01 Q2075.01 CLEANED

Q2419.01 CLEANED Q4031.01 Q4031.01 CLEANED Q4969.01 CLEANED

GCOS 7-V11 TS 9940 UP10

09-001 EN 76677450-004 Rev. E 38

YOUR OPINION ABOUT THIS DOCUMENT

The Customer Service Bulletin is your bulletin. We want to improve it. For this purpose we would like to have your opinion about the presentation and the contents of the present CSB. Does the structure of the document correspond to your expectations when you receive a new Technical Status ? Your comments:

Are the information contained in the VISIBILITY CHANGES, NEW PRODUCTS and IMPROVEMENT chapters detailed enough to have a clear understanding of what the new Technical Status brings ? Your comments:

All your suggestions, recommendations and comments are welcome and will be taken into account (if possible) in the next Technical Status CSB. Your comments:

Please give this form to your Bull S.A.S. representative or mail it to:

Bull S.A.S. GCOS 7 R&D CL – F7/0D25

Rue Jean Jaurès 78340 - LES CLAYES SOUS BOIS

FRANCE