zdds - nokia zdds integration

DD - Remote Debugger Session

DN9813121Issue 4-0 en

# Nokia Corporation 1 (30)

BSC3119Nokia BSC/TCSM, Rel. S12, ProductDocumentation, v.1

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for the useof Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means without theprior written permission of Nokia. The document has been prepared to be used by professionaland properly trained personnel, and the customer assumes full responsibility when using it.Nokia welcomes customer comments as part of the process of continuous development andimprovement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered binding butshall be defined in the agreement made between Nokia and the customer. However, Nokia hasmade all reasonable efforts to ensure that the instructions contained in the document areadequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors.NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENTOR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARYLOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according tothe applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2007. All rights reserved.

2 (30) # Nokia Corporation DN9813121Issue 4-0 en


Contents

Contents 3

List of tables 4

List of figures 5

Summary of changes 7

DD - REMOTE DEBUGGER SESSION 9

DDS START REMOTE SESSION 11

DDE EXECUTE DEBUGGER COMMAND 17

DDT START REMOTE PREPROCESSOR SESSION 23

DDX EXECUTE PREPROCESSOR DEBUGGER COMMAND 27



Contents

List of tables



List of figures



List of figures

Summary of changes

Changes between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

Changes made between issues 4 and 2v

The unit pair parameter was added to the DDE command.

Changes made between issues 2v and 2

An error in the Command list has been corrected.



Summary of changes

DD - REMOTE DEBUGGER SESSION

Use the commands in this command group to open a remote debugger session inthe service terminal of the desired unit.

The remote session can also be opened in the service terminal of the pre-processor unit.

When the session is open, the service terminal commands (debugger commands)can be executed immediately or you can give 1-5 commands to be executed later.The commands in the service terminal program are mainly intended for testingpurposes and for fault location.

The DDT and DDX commands are only used in the BSC and MSC networkelements.

Menu of the command group:

REMOTE DEBUGGER SESSION COMMANDS

? ..... DISPLAY MENU

S: ..... START REMOTE SESSION

E: ..... EXECUTE DEBUGGER COMMAND

T: ..... START REMOTE PREPROCESSOR SESSION

X: ..... EXECUTE PREPROCESSOR DEBUGGER COMMAND

Z; ..... RETURN TO MAIN LEVEL

The commands in this command group are:

DDS START REMOTE SESSION

DDE EXECUTE DEBUGGER COMMAND

DDT START REMOTE PREPROCESSOR SESSION

DDX EXECUTE PREPROCESSOR DEBUGGERCOMMAND



DD - REMOTE DEBUGGER SESSION

DDS START REMOTE SESSIONFunction Use this command at the MML terminal to start a service terminal session in

another unit (a remote debugger session). After opening the session you can givedebugger commands, which control the operation of the operating system andcomputer units.

Note

Only use the debugger commands if you are thoroughly aware of theirpurposes and effects.

Parameters unit identification: buffering;

Syntax DDS: [<unit type> | <own unit> def],

[<subscriber stage> | <unit pair> | 0 def],

[<unit index> | 0 def]:

[<buffering> | NOBUF def];

Parameterexplanations

unit type

Use this parameter to specify the name of the computer unit in which you want tostart the session.

The default value is the local unit; OMU.

You can start a remote debugger session in all computer units located in therelevant network element and connected to the message bus.

subscriber stage

This is the number of the subscriber stage.

Use this parameter when the subscriber stage number is required for identifying acomputer unit.




The parameter value is a decimal number.

The default value is 0.

unit pair

This is the number of the unit pair.

Use this parameter when the unit pair number is required for identifying acomputer unit.



unit index

Use this parameter to specify the unit index.



buffering

BUF outputs are buffered

NOBUF outputs are not buffered (default)

The listings generated by the service terminal software are displayed on theterminal either immediately after the software has produced the text, or when ascreenful of text has been collected in a buffer. The texts are output from thebuffer when the screen becomes full or when the user is expected to give acommand.

Buffering the listings is recommended in order to avoid extra load on the system.

The default value is that outputs are not buffered.

Examples 1. Start a remote debugger session in the CM-0. The listings are not collectedin a buffer. They are displayed as soon as they are generated by the serviceterminal software.

DDS: CM;

or



DDS: CM: NOBUF;

or

DDS: CM, 0: NOBUF;

2. Start a remote debugger session in the CCSU-1. A screenful of listings iscollected before being displayed.

DDS: CCSU, 1: BUF;

3. Start a remote debugger session in the SSU-3-1. The listings are notcollected in a buffer.

DDS: SSU, 3, 1;

or

DDS: SSU, 3, 1: NOBUF;

4. Start a remote debugger session in the Chorus unit DMPG-0. The listingsare not collected in a buffer. They are displayed as soon as they aregenerated by the service terminal software.

DDS: DMPG;

or

DDS: DMPG, 0: NOBUF;

Execution printouts After a command has been executed, the MML program outputs the followingmessage:

COMMAND EXECUTED

The other execution printouts are received from the service terminal software.

At the beginning of a session, the service terminal software displays the followingmessage:

WELCOME TO SERVICE TERMINAL DIALOGUE

At the end of a session, the service terminal software displays the followingmessage:

END OF SERVICE TERMINAL SESSION

Semantic errormessages

If an error occurs, the system outputs a general MML semantic error message.




Execution errormessages

During the MML program execution, any of the following errors may occur:

The MML program first tries to open a session in the relevant unit in the BEservice terminal hand. If the attempt fails, the following message is output:

/* REMOTE SESSION NOT STARTED WITH

COMPUTER xxxx, FAMILY 00BE AND USER yyyyyy

with and explanation; either:

SESSION ON WITH

COMPUTER aaaa, FAMILY bbbb AND USER cccccc */

the service terminal hand is in use

or:

/*** TIME OUT IN REMOTE DEBUGGER SESSION ***/

the service terminal software does not answer within the time limit.

The MML program will then attempt to open a session in the relevant unit in theBF service terminal hand. If the hand is free, you can start the session.

If this also fails, the following message is output:

/*** REMOTE SESSION NOT STARTED WITH

COMPUTER xxxx, FAMILY 00BF AND USER yyyyyy

with an explanation; either:

SESSION ON WITH

COMPUTER aaaa, FAMILY bbbb AND USER cccccc ***/

both service terminal hands are in use. Release the session from computer aaaa, ifpossible.

or:


the service terminal software does not answer within the time limit. No remotedebugger session can be started.

/*** ILLEGAL MESSAGE RECEIVED: received message ***/

The MML program has received an unexpected message.



Requires no user action.

/*** error text related to the OSC status ***/

Failure in communication with the service terminal software.

The session has been interrupted because of an error. Restart the service terminalprocess family.


The service terminal software does not answer within the time limit.

The session has been interrupted because of an error. If you cannot start a newremote session, restart the failed service terminal process family.

The system may also output a general MML execution error message.




DDE EXECUTE DEBUGGER COMMANDFunction Use this command at the MML terminal to start a service terminal session

(remote debugger session) and to execute the service terminal softwarecommands (debugger commands) supplied with parameters. You can use thedebugger commands to control the operation of the operating system andcomputer units.

Note

Only use the debugger commands if you are thoroughly aware of theirpurposes and effects.

Parameters unit identification: input for debugger: listing time;

Syntax DDE: [<unit type> | <own unit> def],

[<subscriber stage> | <unit pair> | 0 def],

[<unit index> | 0 def]:

(<input for debugger>)...:

[<listing time> | <5 min> def];


unit type

Use this parameter to specify the name of the computer unit in which you want tostart the session.

The default value is the local uni; OMU.

You can start a remote debugger session in all computer units that are located inthe relevant network element and connected to the message bus.

subscriber stage

This is the number of the subscriber stage.




Use this parameter when the subscriber stage number is required for identifying acomputer unit.



unit pair

This is the number of the unit pair.

Use this parameter when the unit pair number is required for identifying acomputer unit.



unit index

Use this parameter to specify the unit index.



input for debugger

Use this parameter to execute the debugger command and the related parameters.

Use a character string as the parameter value.

Give at least one debugger command in this block.

You can give a maximum of 5 commands.

listing time

This is the maximum output time.


Use this parameter to specify the latest time after which the output is stopped forcontinually outputting commands, which require the CONTROL-C character tointerrupt the output (for example message monitoring).



The default time is 5 minutes.

The maximum time is 60 - 59 (60 min 59 s), and the minimum 0 - 1 (1 s). If thevalue is 0 - 0, time supervision is not set and character CONTROL-C (03H) is notsent.

Note

This time limit is also valid when large memory areas are output.

Examples 1. Output the statistical data from the error log in the operating system and theexception condition interrupt records (memory protection errors) in the M-0. The listing ends after 1 minute at the latest.

DDE: M: "ZSLS", "LP": 1-0;

or

DDE: M, 0: "ZSLS;", "ZSLP;": 1-0;

2. Output the operating system error counters and the value of counter 109Hin the CM-0. The listing time is not limited.

DDE: CM: "ZSCFE", "C:109": 0-0;

or

DDE: CM, 0: "ZSCFE;", "ZSC:109;": 0-0;

3. Output statistical data from the OMU computer log and the error log as awhole. The third command is used to examine the log writings made by theBOMBER program block (process identifier A1). The log empties after theoutput.

DDE: : "ZGI", "ZGDC", "ZGSC:,A1", "ZGC";

4. Output the buffers that the BOMBER program block (A1) of the OMU hasreserved.

DDE: : "ZSBP:A1";

5. Monitor all messages coming to the OMU's BOMBER program block (A1)from any computer. The monitoring stops after 10 minutes at the latest.

DDE: : "ZOQ:A1,0,1,FFFF,FFFF,FFFF,FFFF": 10-0;

6. Restart process family A1 in the OMU.

DDE: : "ZODR:A1";




7. Output the load of processes BE and BF located in the OMU. Theintegration time is 1 second.

DDE: : "ZSR:1:BE:BF";

8. Output 64 bytes from memory location G54.60 in the CM-0.

DDE: CM: "ZDD:G54.60,+3F";

or

DDE: CM, 0: "ZDD:G54.60,+3F;";

9. Output operating system log and the computer log as a whole in MXU–0.

DDE: MXU, 0: "olog —s", "clog —s —a";

10. Output all system configuration environment variables, status of all actorsand information about all threads in Chorus computer DMPG–27.

DDE: DMPG, 27: "sysenv", "alist", "tlist";

11. Output unit starting phase output texts and boot actors version stamps inChorus unit DMPG-27.

DDE: DMPG, 27: "cat /var/daqtor/phaseoutput.txt","cat /image/sys_bank/versions.txt";

12. Monitore messages of Chorus actor 143 in unit TPG-4 for 7 minutes.

DDE: TPG, 4: "dxfload -n CSXDMXMO -d -u 0 -o /bin/dmxmon.gz", "dmxmon -f 143": 7–0;

Execution printouts After the command has been executed, the MML program displays the followingmessage:

COMMAND EXECUTED

The other execution printouts are generated by the service terminal software.

At the beginning of a session, the service terminal software displays the followingmessage:

WELCOME TO SERVICE TERMINAL DIALOGUE




During the MML program execution, any of the following errors may occur:



The MML program first tries to open a session in the relevant unit in the BEservice terminal hand. If the attempt fails, the following message is output:

/* REMOTE SESSION NOT STARTED WITH

COMPUTER xxxx, FAMILY 00BE AND USER yyyyyy


SESSION ON WITH

COMPUTER aaaa, FAMILY bbbb AND USER cccccc */

The service terminal hand is in use

or:



The MML program will then attempt to open a session in the service terminalhand, BF, in the unit involved. If the hand is free, you can start the session.

If this also fails, the following message is output:

/*** REMOTE SESSION NOT STARTED WITH

COMPUTER xxxx, FAMILY 00BF AND USER yyyyyy


SESSION ON WITH

COMPUTER aaaa, FAMILY bbbb AND USER cccccc ***/

Both service terminal hands are in use. Release the session from computer aaaa, ifpossible.

or:


The service terminal software does not answer within the time limit. No remotedebugger session can be started.

If an error occurs and the command execution fails during the remote debuggersession, the following message is output:

/*** SESSION ABORTED ***/

/*** DEBUGGER COMMAND EXECUTION ERROR ***/




The command specified at the service terminal was incorrect. The execution ofthe command is interrupted.

Enter the command in the correct form and restart the command execution.

/*** ILLEGAL MESSAGE RECEIVED: received message

The MML program has received an unexpected message

No user action is required.

/*** error text related to the OSC status ***/

Failure in communication with the service terminal software.

The session has been interrupted because of an error. Restart the service terminalprocess family.



A session has been interrupted because of an error. If a new remote session cannotbe started, restart the service terminal process family.




DDT START REMOTE PREPROCESSORSESSIONFunction Use the DDT command at the MML terminal to start a session in the service

terminal program of a pre-processor. After opening the session you can use theservice terminal commands (debugger commands) to control the operation of theoperating system and computer units.

Note: Only use the debugger commands if you are thoroughly aware of theirpurposes and effects.

Parameters unit identification: buffering;

Syntax DDT: <unit type>, <unit index>:

[<buffering> | NOBUF def];


unit type

Specifies the name of the pre-processor unit in which you want to start thesession.

You can start service terminal sessions (remote debugger sessions) in all pre-processor units that are equipped with local user software that supports a remotedebugger session.

This parameter is obligatory and there is no default value.

unit index

Specifies the index of the computer unit.



buffering




BUF outputs are buffered

NOBUF outputs are not buffered (default)

The listings generated by the service terminal software are displayed on theterminal either immediately after the software has produced the text or when ascreenful of text has been collected in a buffer. The texts are output from thebuffer when the screen becomes full or when the user is expected to give acommand.

We recommend buffering the listings in order to avoid extra load on the system.

The default value is that outputs are not buffered.

Examples 1. Start a session in the ECU-64. The listings are not buffered, they aredisplayed as soon as the service terminal software generates the texts thatshould be displayed.

DDT: ECU, 64;

or

DDT: ECU, 64: NOBUF;

2. Start a remote debugger session in the ET-124. A screenful of listings iscollected before being displayed.

DDT: ET, 124: BUF;

3. Start a remote debugger session in the DIPC-98. The listings are notcollected in a buffer.

DDT: DIPC, 98: NOBUF;

Execution printouts After a command has been executed, the MML program outputs the followingmessage:

COMMAND EXECUTED

The MML program adds the type and index of the pre-processor device to thecommand prompt generated by service terminal software.

ECU_064:MAN>


At the beginning of a session, the service terminal software (for example in theECU) displays the following message:



WELCOME TO THE ECU LOCAL TERMINAL DIALOGUE

At the end of a session, the service terminal software displays the followingmessage:

END OF ECU LOCAL SESSION




/*** USER AUTHORIZATION FAILURE ***/

/*** DX ERROR: 514 ***/

/*** NO AUTHORITIES FOR SESSION ***/

You have entered an invalid user name or password.

Make sure the user information you enter is correct.

/*** REMOTE SESSION NOT STARTED WITH PREPROCESSOR ***/

/*** DX ERROR: 11457 ***/

/*** NO FREE REMOTE MMI CONNECTIONS ***/

It was not possible to start the session in the service terminal program of thespecified pre-processor unit.

A local session has already been started in an MML terminal. Close the session orwait until it becomes free.

/*** A LOCAL USER HAS OPENED A SERVICE TERMINAL SESSION ***/

There is already a remote session in the service terminal program.

Close the local session or wait until it becomes free.


The service terminal software has not answered within the time limit.

Restart the session.



Requires no user action.





DDX EXECUTE PREPROCESSOR DEBUGGERCOMMANDFunction Use the DDX command at the MML terminal to start a service terminal session

(remote debugger session) in the service terminal software of a pre-processor, andto execute the service terminal commands (debugger commands) supplied withparameters. After opening the session you can use the debugger commands tocontrol the operation of the operating system and computer units.

Note: Only use the debugger commands if you are thoroughly aware of theirpurposes and effects.

Parameters unit identification: local user communications commands: time limit;

Syntax DDT: <unit type>, <unit index>:

[<input for debugger>]...:

[<listing time> | <5 min> def];


unit type

Specifies the name of the pre-processor unit in which you want to start thesession.

You can start a remote debugger session in all pre-processor units that areequipped with local user software that supports a remote debugger session.


unit index

Specifies the index of the computer unit.





DDX EXECUTE PREPROCESSOR DEBUGGER COMMAND

input for debugger

This is the debugger command to be executed and its related parameters.

Use a character string as the parameter value.

Give at least one debugger command in this block.

You can give a maximum of 5 commands.

listing time

This is the maximum output time.


In the continually outputting commands which require the CONTROL-Ccharacter to interrupt the output (for example message monitoring), use thisparameter to specify the time after which the output is stopped at the latest.

The default time is 5 minutes.

The maximum time is 60 - 59 (60 min 59 s) and the minimum 0 - 1 (1 s). If thevalue is 0 - 0, time supervision is not set and the CONTROL-C (03H) character isnot sent.

Note: The time limit is also valid when large memory areas are output.

Examples 1. Output 16 bytes from memory location 1000.0 in TCSM-17. The output isended after 20 seconds at the latest.

DDX: TCSM, 17: "ZDD:1000.0,10": 0-20;

2. Output 255 bytes from memory location C500.0 in ECU-65. The outputwidth is 16 bytes.

DDX: ECU, 65: "ZDD:C500.0,FF,F;";

3. Output the parameters for the transcoder handling timeslot 12 on internalPCM circuit 2 in TCSM 128.

DDX: TCSM, 128: "ZRC:2,12";

4. Search for the character string 'LUCECU' in the memory of the ECU-64starting from address C500.0, in the area of 255 bytes. Also display thestate data for process F2. The output is ended at the latest 30 seconds afterthe command execution began.



DDX: ECU, 64: "ZDE:C500.0,FF,'LUCECU;", "ZOM:F2;": 0-30;

5. Output the identifier data concerning the 'LUC' program block found in theECU-65. Also output the terminal settings for the service terminal andcheck whether the service terminal has received any messages. Calculatethe check sum for the first 256 bytes in memory area C500.0.

DDX: ECU, 65: "ZSX:LUC;", "ZT", "ZOT", "ZDP:C500.0,FF;";

6. Give “the following command Y” as a second parameter to confirm thatthe command ABC will be executed (the command requires Y/Nconfirmation). The command is sent to ECU–64 pre-processor to beexecuted.

ZDDX:ECU,64:”ABC;”,”Y”;

Execution printouts After the command has been executed, the MML program displays the followingmessage:

COMMAND EXECUTED

The MML program adds the type and index of the pre-processor device to thecommand prompt generated by service terminal software.

ECU_064:MAN>


At the beginning of a session, the service terminal software (for example in theECU) displays the following message:

WELCOME TO THE ECU LOCAL TERMINAL DIALOGUE




/*** REMOTE SESSION NOT STARTED WITH PREPROCESSOR ***/

/*** DX ERROR: 11457 ***/

/*** NO FREE REMOTE MMI CONNECTIONS ***/

It was not possible to start the session in the service terminal program of thespecified pre-processor unit.

A local session has already been started in an MML terminal. Close the session orwait until it becomes free.

/*** A LOCAL USER HAS OPENED A SERVICE TERMINAL SESSION ***/



DDX EXECUTE PREPROCESSOR DEBUGGER COMMAND

There is already a remote session in the service terminal program.

Close the local session or wait until it becomes free.



Restart the session.



Requires no user actions.

If an error occurs during the session, the following message is output:

/*** SESSION ABORTED ***/

/*** DX ERROR: ***/

/*** specification of the error ***/

An error has occured during execution.

Find out the reason for the error from the error code and try to fix the error.




zdds - nokia zdds integration

Documents

copyright nokia corporation

nokia logo

permission of nokia

nokia hasmade

document issues

remote session

document areadequate

remote preprocessor