Workflow Manager Messages and Troubleshooting - Micro Focus · 2014-05-15 · Workflow Manager...

Workflow Manager Messages and

Troubleshooting

Workflow Manager Messages and Troubleshooting

Page: 2

Micro Focus

The Lawn

22-30 Old Bath Road

Newbury, Berkshire RG14 1QN

UK

http://www.microfocus.com

Copyright © 2011-2013 Micro Focus. All rights reserved.

MICRO FOCUS and the Micro Focus logo are trademarks or registered

trademarks of Micro Focus or its subsidiaries or affiliated

companies in the United States, United Kingdom and other countries.

All other marks are the property of their respective owners.

http://www.microfocus.com/


Page: 3

Contents

1 Introduction................................................................................................. 18

2 Error Messages ............................................................................................ 22

2.1 TAURUS Core (TSCOR) ..................................................................................................................... 22

2.1.1 TSCOR0001 ........................................................................................................................................ 22

2.1.2 TSCOR0002 ........................................................................................................................................ 22

2.1.3 TSCOR0003 ........................................................................................................................................ 23

2.1.4 TSCOR0004 ........................................................................................................................................ 23

2.1.5 TSCOR0005 ........................................................................................................................................ 24

2.1.6 TSCOR0007 ........................................................................................................................................ 24

2.1.7 TSCOR0008 ........................................................................................................................................ 24

2.1.8 TSCOR0009 ........................................................................................................................................ 25

2.1.9 TSCOR0010 ........................................................................................................................................ 25

2.1.10 TSCOR0011 ................................................................................................................................... 25

2.1.11 TSCOR0012 ................................................................................................................................... 25

2.1.12 TSCOR0013 ................................................................................................................................... 26

2.1.13 TSCOR0014 ................................................................................................................................... 26

2.1.14 TSCOR0019 ................................................................................................................................... 26

2.1.15 TSCOR0024 ................................................................................................................................... 27

2.1.16 TSCOR0025 ................................................................................................................................... 27

2.1.17 TSCOR0026 ................................................................................................................................... 27

2.1.18 TSCOR0030 ................................................................................................................................... 28

2.1.19 TSCOR0031 ................................................................................................................................... 28

2.1.20 TSCOR0032 ................................................................................................................................... 28

2.1.21 TSCOR0033 ................................................................................................................................... 29

2.1.22 TSCOR0034 ................................................................................................................................... 29

2.1.23 TSCOR0035 ................................................................................................................................... 29

2.1.24 TSCOR0036 ................................................................................................................................... 29

2.1.25 TSCOR0037 ................................................................................................................................... 30

2.1.26 TSCOR0040 ................................................................................................................................... 30

2.1.27 TSCOR0041 ................................................................................................................................... 30

2.1.28 TSCOR0042 ................................................................................................................................... 31

2.1.29 TSCOR0043 ................................................................................................................................... 31


Page: 4

2.1.30 TSCOR0044 ................................................................................................................................... 31

2.1.31 TSCOR0045 ................................................................................................................................... 32

2.1.32 TSCOR0046 ................................................................................................................................... 32

2.1.33 TSCOR0047 ................................................................................................................................... 32

2.1.34 TSCOR0048 ................................................................................................................................... 32

2.1.35 TSCOR0049 ................................................................................................................................... 33

2.1.36 TSCOR0050 ................................................................................................................................... 33

2.1.37 TSCOR0051 ................................................................................................................................... 33

2.1.38 TSCOR0052 ................................................................................................................................... 34

2.1.39 TSCOR0054 ................................................................................................................................... 34

2.1.40 TSCOR0055 ................................................................................................................................... 34

2.1.41 TSCOR0056 ................................................................................................................................... 35

2.1.42 TSCOR0057 ................................................................................................................................... 35

2.1.43 TSCOR0058 ................................................................................................................................... 35

2.1.44 TSCOR0059 ................................................................................................................................... 35

2.1.45 TSCOR0060 ................................................................................................................................... 36

2.1.46 TSCOR0061 ................................................................................................................................... 36

2.1.47 TSCOR0062 ................................................................................................................................... 36

2.1.48 TSCOR0063 ................................................................................................................................... 37

2.1.49 TSCOR0064 ................................................................................................................................... 37

2.1.50 TSCOR0065 ................................................................................................................................... 37

2.1.51 TSCOR0066 ................................................................................................................................... 38

2.1.52 TSCOR0067 ................................................................................................................................... 38

2.1.53 TSCOR0068 ................................................................................................................................... 38

2.1.54 TSCOR0069 ................................................................................................................................... 39

2.1.55 TSCOR0070 ................................................................................................................................... 39

2.1.56 TSCOR0071 ................................................................................................................................... 39

2.1.57 TSCOR0072 ................................................................................................................................... 39

2.1.58 TSCOR0073 ................................................................................................................................... 40

2.1.59 TSCOR0074 ................................................................................................................................... 40

2.1.60 TSCOR0076 ................................................................................................................................... 40

2.1.61 TSCOR0077 ................................................................................................................................... 41

2.1.62 TSCOR0078 ................................................................................................................................... 41

2.1.63 TSCOR0079 ................................................................................................................................... 41


Page: 5

2.1.64 TSCOR0080 ................................................................................................................................... 41

2.1.65 TSCOR0081 ................................................................................................................................... 42

2.1.66 TSCOR0084 ................................................................................................................................... 42

2.1.67 TSCOR0087 ................................................................................................................................... 42

2.1.68 TSCOR0089 ................................................................................................................................... 42

2.1.69 TSCOR0090 ................................................................................................................................... 43

2.1.70 TSCOR0091 ................................................................................................................................... 43

2.1.71 TSCOR0092 ................................................................................................................................... 43

2.1.72 TSCOR0093 ................................................................................................................................... 44

2.1.73 TSCOR0094 ................................................................................................................................... 44

2.1.74 TSCOR0095 ................................................................................................................................... 44

2.1.75 TSCOR0096 ................................................................................................................................... 45

2.1.76 TSCOR0097 ................................................................................................................................... 45

2.1.77 TSCOR0099 ................................................................................................................................... 45

2.1.78 TSCOR0100 ................................................................................................................................... 45

2.1.79 TSCOR0102 ................................................................................................................................... 46

2.1.80 TSCOR0103 ................................................................................................................................... 46

2.1.81 TSCOR0104 ................................................................................................................................... 46

2.1.82 TSCOR0105 ................................................................................................................................... 47

2.1.83 TSCOR0107 ................................................................................................................................... 47

2.1.84 TSCOR0108 ................................................................................................................................... 47

2.1.85 TSCOR0109 ................................................................................................................................... 48

2.1.86 TSCOR0110 ................................................................................................................................... 48

2.1.87 TSCOR0111 ................................................................................................................................... 48

2.1.88 TSCOR0112 ................................................................................................................................... 49

2.1.89 TSCOR0113 ................................................................................................................................... 49

2.1.90 TSCOR0114 ................................................................................................................................... 49

2.1.91 TSCOR0115 ................................................................................................................................... 50

2.1.92 TSCOR0116 ................................................................................................................................... 50

2.1.93 TSCOR0117 ................................................................................................................................... 50

2.1.94 TSCOR0118 ................................................................................................................................... 51

2.1.95 TSCOR0119 ................................................................................................................................... 51

2.1.96 TSCOR0121 ................................................................................................................................... 51

2.1.97 TSCOR0122 ................................................................................................................................... 51


Page: 6

2.1.98 TSCOR0123 ................................................................................................................................... 52

2.1.99 TSCOR0124 ................................................................................................................................... 52

2.1.100 TSCOR0125 ................................................................................................................................... 52

2.1.101 TSCOR0126 ................................................................................................................................... 53

2.1.102 TSCOR0127 ................................................................................................................................... 53

2.1.103 TSCOR0128 ................................................................................................................................... 53

2.1.104 TSCOR0129 ................................................................................................................................... 54

2.1.105 TSCOR0130 ................................................................................................................................... 54

2.1.106 TSCOR0131 ................................................................................................................................... 54

2.1.107 TSCOR0132 ................................................................................................................................... 55

2.1.108 TSCOR0133 ................................................................................................................................... 55

2.1.109 TSCOR0134 ................................................................................................................................... 55

2.1.110 TSCOR0136 ................................................................................................................................... 55

2.1.111 TSCOR0137 ................................................................................................................................... 56

2.1.112 TSCOR0138 ................................................................................................................................... 56

2.1.113 TSCOR0139 ................................................................................................................................... 56

2.1.114 TSCOR0140 ................................................................................................................................... 57

2.1.115 TSCOR0141 ................................................................................................................................... 57

2.1.116 TSCOR0142 ................................................................................................................................... 57

2.1.117 TSCOR0143 ................................................................................................................................... 58

2.1.118 TSCOR0144 ................................................................................................................................... 58

2.1.119 TSCOR0145 ................................................................................................................................... 58

2.1.120 TSCOR0146 ................................................................................................................................... 59

2.1.121 TSCOR0147 ................................................................................................................................... 59

2.1.122 TSCOR0148 ................................................................................................................................... 59

2.1.123 TSCOR0149 ................................................................................................................................... 59

2.1.124 TSCOR0150 ................................................................................................................................... 60

2.1.125 TSCOR0151 ................................................................................................................................... 60

2.1.126 TSCOR0152 ................................................................................................................................... 60

2.1.127 TSCOR0153 ................................................................................................................................... 61

2.1.128 TSCOR0154 ................................................................................................................................... 61

2.1.129 TSCOR0155 ................................................................................................................................... 62

2.1.130 TSCOR0156 ................................................................................................................................... 62

2.1.131 TSCOR0157 ................................................................................................................................... 62


Page: 7

2.1.132 TSCOR0158 ................................................................................................................................... 62

2.1.133 TSCOR0159 ................................................................................................................................... 63

2.1.134 TSCOR0160 ................................................................................................................................... 63

2.1.135 TSCOR0161 ................................................................................................................................... 63

2.1.136 TSCOR0163 ................................................................................................................................... 64

2.1.137 TSCOR0164 ................................................................................................................................... 64

2.1.138 TSCOR0165 ................................................................................................................................... 64

2.1.139 TSCOR0166 ................................................................................................................................... 64

2.2 TAURUS For z/Server (TSZSV) .......................................................................................................... 65

2.2.1 TSZSV0001 .......................................................................................................................................... 65

2.2.2 TSZSV0002 .......................................................................................................................................... 65

2.2.3 TSZSV0003 .......................................................................................................................................... 65

2.2.4 TSZSV0004 .......................................................................................................................................... 66

2.2.5 TSZSV0005 .......................................................................................................................................... 66

2.2.6 TSZSV0006 .......................................................................................................................................... 66

2.2.7 TSZSV0007 .......................................................................................................................................... 67

2.2.8 TSZSV0008 .......................................................................................................................................... 67

2.2.9 TSZSV0009 .......................................................................................................................................... 67

2.2.10 TSZSV0010 ..................................................................................................................................... 67

2.2.11 TSZSV0011 ..................................................................................................................................... 68

2.2.12 TSZSV0012 ..................................................................................................................................... 68

2.2.13 TSZSV0013 ..................................................................................................................................... 68

2.2.14 TSZSV0014 ..................................................................................................................................... 69

2.2.15 TSZSV0015 ..................................................................................................................................... 69

2.2.16 TSZSV0016 ..................................................................................................................................... 69

2.2.17 TSZSV0017 ..................................................................................................................................... 70

2.2.18 TSZSV0018 ..................................................................................................................................... 70

2.2.19 TSZSV0019 ..................................................................................................................................... 70

2.2.20 TSZSV0020 ..................................................................................................................................... 71

2.2.21 TSZSV0021 ..................................................................................................................................... 71

2.2.22 TSZSV0022 ..................................................................................................................................... 71

2.2.23 TSZSV0023 ..................................................................................................................................... 72

2.2.24 TSZSV0025 ..................................................................................................................................... 72

2.3 TAURUS Subsystem MVS (TSMVS) ................................................................................................... 72


Page: 8

2.3.1 TSMVS0001 ......................................................................................................................................... 72

2.3.2 TSMVS0002 ......................................................................................................................................... 72

2.3.3 TSMVS0003 ......................................................................................................................................... 73

2.3.4 TSMVS0005 ......................................................................................................................................... 73

2.3.5 TSMVS0006 ......................................................................................................................................... 74

2.3.6 TSMVS0007 ......................................................................................................................................... 74

2.3.7 TSMVS0008 ......................................................................................................................................... 74

2.3.8 TSMVS0009 ......................................................................................................................................... 75

2.3.9 TSMVS0010 ......................................................................................................................................... 75

2.3.10 TSMVS0011..................................................................................................................................... 75

2.3.11 TSMVS0012..................................................................................................................................... 76

2.3.12 TSMVS0013..................................................................................................................................... 76

2.3.13 TSMVS0014..................................................................................................................................... 76

2.3.14 TSMVS0015..................................................................................................................................... 77

2.3.15 TSMVS0016..................................................................................................................................... 77

2.3.16 TSMVS0023..................................................................................................................................... 77

2.3.17 TSMVS0024..................................................................................................................................... 78

2.3.18 TSMVS0025..................................................................................................................................... 78

2.3.19 TSMVS0026..................................................................................................................................... 79

2.4 TAURUS UI (TSUIN) ............................................................................................................................ 79

2.4.1 TSUIN0001 .......................................................................................................................................... 79

2.4.2 TSUIN0002 .......................................................................................................................................... 79

2.4.3 TSUIN0003 .......................................................................................................................................... 80

2.4.4 TSUIN0004 .......................................................................................................................................... 80

2.4.5 TSUIN0005 .......................................................................................................................................... 80

2.4.6 TSUIN0006 .......................................................................................................................................... 80

2.4.7 TSUIN0007 .......................................................................................................................................... 81

2.4.8 TSUIN0008 .......................................................................................................................................... 81

2.4.9 TSUIN0009 .......................................................................................................................................... 81

2.4.10 TSUIN0010 ..................................................................................................................................... 82

2.4.11 TSUIN0011 ..................................................................................................................................... 82

2.4.12 TSUIN0012 ..................................................................................................................................... 82

2.4.13 TSUIN0013 ..................................................................................................................................... 82

2.4.14 TSUIN0014 ..................................................................................................................................... 83


Page: 9

2.4.15 TSUIN0016 ..................................................................................................................................... 83

2.4.16 TSUIN0017 ..................................................................................................................................... 83

2.4.17 TSUIN0018 ..................................................................................................................................... 84

2.4.18 TSUIN0019 ..................................................................................................................................... 84

2.4.19 TSUIN0021 ..................................................................................................................................... 84

2.4.20 TSUIN0024 ..................................................................................................................................... 85

2.4.21 TSUIN0025 ..................................................................................................................................... 85

2.4.22 TSUIN0026 ..................................................................................................................................... 85

2.4.23 TSUIN0027 ..................................................................................................................................... 86

2.4.24 TSUIN0028 ..................................................................................................................................... 86

2.4.25 TSUIN0029 ..................................................................................................................................... 86

2.4.26 TSUIN0030 ..................................................................................................................................... 87

2.4.27 TSUIN0031 ..................................................................................................................................... 87

2.4.28 TSUIN0032 ..................................................................................................................................... 87

2.4.29 TSUIN0033 ..................................................................................................................................... 88

2.4.30 TSUIN0034 ..................................................................................................................................... 88

2.4.31 TSUIN0035 ..................................................................................................................................... 88

2.4.32 TSUIN0036 ..................................................................................................................................... 88

2.4.33 TSUIN0037 ..................................................................................................................................... 89

2.4.34 TSUIN0038 ..................................................................................................................................... 89

2.4.35 TSUIN0039 ..................................................................................................................................... 89

2.4.36 TSUIN0040 ..................................................................................................................................... 89

2.4.37 TSUIN0041 ..................................................................................................................................... 90

2.4.38 TSUIN0042 ..................................................................................................................................... 90

2.4.39 TSUIN0043 ..................................................................................................................................... 90

2.4.40 TSUIN0044 ..................................................................................................................................... 91

2.4.41 TSUIN0045 ..................................................................................................................................... 91

2.4.42 TSUIN0047 ..................................................................................................................................... 91

2.4.43 TSUIN0048 ..................................................................................................................................... 92

2.4.44 TSUIN0049 ..................................................................................................................................... 92

2.4.45 TSUIN0050 ..................................................................................................................................... 92

2.4.46 TSUIN0051 ..................................................................................................................................... 93

2.4.47 TSUIN0052 ..................................................................................................................................... 93

2.4.48 TSUIN0053 ..................................................................................................................................... 93


Page: 10

2.4.49 TSUIN0054 ..................................................................................................................................... 94

2.4.50 TSUIN0055 ..................................................................................................................................... 94

2.4.51 TSUIN0057 ..................................................................................................................................... 94

2.4.52 TSUIN0058 ..................................................................................................................................... 95

2.4.53 TSUIN0059 ..................................................................................................................................... 95

2.4.54 TSUIN0060 ..................................................................................................................................... 95

2.4.55 TSUIN0061 ..................................................................................................................................... 96

2.4.56 TSUIN0062 ..................................................................................................................................... 96

2.4.57 TSUIN0063 ..................................................................................................................................... 96

2.4.58 TSUIN0064 ..................................................................................................................................... 97

2.4.59 TSUIN0065 ..................................................................................................................................... 97

2.4.60 TSUIN0066 ..................................................................................................................................... 97

2.4.61 TSUIN0067 ..................................................................................................................................... 98

2.4.62 TSUIN0068 ..................................................................................................................................... 98

2.4.63 TSUIN0069 ..................................................................................................................................... 98

2.4.64 TSUIN0070 ..................................................................................................................................... 99

2.4.65 TSUIN0071 ..................................................................................................................................... 99

2.4.66 TSUIN0072 ..................................................................................................................................... 99

2.4.67 TSUIN0073 .................................................................................................................................. 100

2.4.68 TSUIN0074 .................................................................................................................................. 100

2.4.69 TSUIN0075 .................................................................................................................................. 100

2.4.70 TSUIN0077 .................................................................................................................................. 101

2.4.71 TSUIN0078 .................................................................................................................................. 101

2.4.72 TSUIN0079 .................................................................................................................................. 101

2.4.73 TSUIN0080 .................................................................................................................................. 102

2.4.74 TSUIN0081 .................................................................................................................................. 102

2.4.75 TSUIN0082 .................................................................................................................................. 102

2.4.76 TSUIN0083 .................................................................................................................................. 103

2.4.77 TSUIN0084 .................................................................................................................................. 103

2.4.78 TSUIN0085 .................................................................................................................................. 103

2.4.79 TSUIN0086 .................................................................................................................................. 104

2.4.80 TSUIN0087 .................................................................................................................................. 104

2.4.81 TSUIN0088 .................................................................................................................................. 104

2.4.82 TSUIN0089 .................................................................................................................................. 105


Page: 11

2.4.83 TSUIN0090 .................................................................................................................................. 105

2.4.84 TSUIN0091 .................................................................................................................................. 105

2.5 TAURUS UI Views (TSUIV) .............................................................................................................. 105

2.5.1 TSUIV0002 ....................................................................................................................................... 105

2.5.2 TSUIV0003 ....................................................................................................................................... 106

2.5.3 TSUIV0004 ....................................................................................................................................... 106

2.5.4 TSUIV0005 ....................................................................................................................................... 107

2.5.5 TSUIV0006 ....................................................................................................................................... 107

2.5.6 TSUIV0007 ....................................................................................................................................... 107

2.5.7 TSUIV0008 ....................................................................................................................................... 108

2.5.8 TSUIV0009 ....................................................................................................................................... 108

2.5.9 TSUIV0010 ....................................................................................................................................... 108

2.5.10 TSUIV0011 ................................................................................................................................... 109

2.6 TAURUS Meta Model (TSMDL) ...................................................................................................... 109

2.6.1 TSMDL0001 ..................................................................................................................................... 109

2.6.2 TSMDL0002 ..................................................................................................................................... 109

2.7 TAURUS Meta Model Editor (TSMET) .......................................................................................... 110

2.7.1 TSMET0001 ...................................................................................................................................... 110

2.7.2 TSMET0002 ...................................................................................................................................... 110

2.7.3 TSMET0003 ...................................................................................................................................... 110

2.7.4 TSMET0004 ...................................................................................................................................... 111

2.7.5 TSMET0006 ...................................................................................................................................... 111

2.8 zExplorer For z/Server (TSXZS) ..................................................................................................... 111

2.8.1 TSXZS0001 ...................................................................................................................................... 111

2.8.2 TSXZS0002 ...................................................................................................................................... 112

2.8.3 TSXZS0003 ...................................................................................................................................... 112

2.8.4 TSXZS0004 ...................................................................................................................................... 112

2.8.5 TSXZS0005 ...................................................................................................................................... 113

2.8.6 TSXZS0006 ...................................................................................................................................... 113

2.8.7 TSXZS0011 ...................................................................................................................................... 113

2.8.8 TSXZS0012 ...................................................................................................................................... 114

2.8.9 TSXZS0015 ...................................................................................................................................... 114

2.8.10 TSXZS0016 .................................................................................................................................. 114

2.8.11 TSXZS0018 .................................................................................................................................. 115


Page: 12

2.8.12 TSXZS0022 .................................................................................................................................. 115

2.8.13 TSXZS0023 .................................................................................................................................. 116

2.8.14 TSXZS0025 .................................................................................................................................. 116

2.8.15 TSXZS0026 .................................................................................................................................. 116

2.8.16 TSXZS0027 .................................................................................................................................. 117

2.8.17 TSXZS0028 .................................................................................................................................. 117

2.8.18 TSXZS0029 .................................................................................................................................. 117

2.8.19 TSXZS0030 .................................................................................................................................. 117

2.8.20 TSXZS0031 .................................................................................................................................. 118

2.8.21 TSXZS0032 .................................................................................................................................. 118

2.8.22 TSXZS0033 .................................................................................................................................. 118

2.8.23 TSXZS0034 .................................................................................................................................. 119

2.8.24 TSXZS0035 .................................................................................................................................. 119

2.8.25 TSXZS0036 .................................................................................................................................. 119

2.8.26 TSXZS0037 .................................................................................................................................. 120

2.8.27 TSXZS0042 .................................................................................................................................. 120

2.9 zExplorer Subsystem JES (TSXJE) .................................................................................................... 120

2.9.1 TSXJE0001 ........................................................................................................................................ 120

2.9.2 TSXJE0002 ........................................................................................................................................ 121

2.9.3 TSXJE0003 ........................................................................................................................................ 121

2.9.4 TSXJE0004 ........................................................................................................................................ 121

2.9.5 TSXJE0005 ........................................................................................................................................ 121

2.9.6 TSXJE0006 ........................................................................................................................................ 122

2.9.7 TSXJE0007 ........................................................................................................................................ 122

2.9.8 TSXJE0008 ........................................................................................................................................ 122

2.9.9 TSXJE0009 ........................................................................................................................................ 123

2.9.10 TSXJE0010 ................................................................................................................................... 123

2.9.11 TSXJE0011 ................................................................................................................................... 123

2.10 zExplorer Subsystem MVS (TSXMV) .............................................................................................. 124

2.10.1 TSXMV0001 ................................................................................................................................ 124

2.10.2 TSXMV0002 ................................................................................................................................ 124

2.10.3 TSXMV0003 ................................................................................................................................ 124

2.10.4 TSXMV0004 ................................................................................................................................ 125

2.10.5 TSXMV0005 ................................................................................................................................ 125


Page: 13

2.10.6 TSXMV0007 ................................................................................................................................ 125

2.10.7 TSXMV0008 ................................................................................................................................ 125

2.10.8 TSXMV0009 ................................................................................................................................ 126

2.10.9 TSXMV0010 ................................................................................................................................ 126

2.10.10 TSXMV0011 ................................................................................................................................ 126

2.10.11 TSXMV0012 ................................................................................................................................ 127

2.10.12 TSXMV0013 ................................................................................................................................ 127

2.10.13 TSXMV0014 ................................................................................................................................ 127

2.10.14 TSXMV0015 ................................................................................................................................ 128

2.10.15 TSXMV0016 ................................................................................................................................ 128

2.10.16 TSXMV0017 ................................................................................................................................ 128

2.10.17 TSXMV0018 ................................................................................................................................ 129

2.10.18 TSXMV0019 ................................................................................................................................ 129

2.10.19 TSXMV0020 ................................................................................................................................ 129

2.10.20 TSXMV0021 ................................................................................................................................ 130

2.10.21 TSXMV0022 ................................................................................................................................ 130

2.10.22 TSXMV0023 ................................................................................................................................ 130

2.10.23 TSXMV0024 ................................................................................................................................ 130

2.10.24 TSXMV0025 ................................................................................................................................ 131

2.10.25 TSXMV0026 ................................................................................................................................ 131

2.10.26 TSXMV0027 ................................................................................................................................ 131

2.10.27 TSXMV0028 ................................................................................................................................ 131

2.10.28 TSXMV0029 ................................................................................................................................ 132

2.10.29 TSXMV0030 ................................................................................................................................ 132

2.10.30 TSXMV0031 ................................................................................................................................ 132

2.10.31 TSXMV0032 ................................................................................................................................ 133

2.10.32 TSXMV0035 ................................................................................................................................ 133

2.10.33 TSXMV0036 ................................................................................................................................ 133

2.10.34 TSXMV0037 ................................................................................................................................ 133

2.10.35 TSXMV0038 ................................................................................................................................ 134

2.10.36 TSXMV0040 ................................................................................................................................ 134

2.10.37 TSXMV0041 ................................................................................................................................ 134

2.10.38 TSXMV0042 ................................................................................................................................ 135

2.10.39 TSXMV0043 ................................................................................................................................ 135


Page: 14

2.10.40 TSXMV0044 ................................................................................................................................ 135

2.10.41 TSXMV0045 ................................................................................................................................ 136

2.10.42 TSXMV0046 ................................................................................................................................ 136

2.10.43 TSXMV0047 ................................................................................................................................ 136

2.10.44 TSXMV0048 ................................................................................................................................ 136

2.10.45 TSXMV0049 ................................................................................................................................ 137

2.10.46 TSXMV0050 ................................................................................................................................ 137

2.10.47 TSXMV0051 ................................................................................................................................ 137

2.10.48 TSXMV0052 ................................................................................................................................ 138

2.10.49 TSXMV0054 ................................................................................................................................ 138

2.10.50 TSXMV0055 ................................................................................................................................ 138

2.10.51 TSXMV0056 ................................................................................................................................ 138

2.10.52 TSXMV0057 ................................................................................................................................ 139

2.10.53 TSXMV0058 ................................................................................................................................ 139

2.10.54 TSXMV0059 ................................................................................................................................ 139

2.10.55 TSXMV0060 ................................................................................................................................ 140

2.10.56 TSXMV0061 ................................................................................................................................ 140

2.10.57 TSXMV0062 ................................................................................................................................ 140

2.10.58 TSXMV0063 ................................................................................................................................ 140

2.10.59 TSXMV0064 ................................................................................................................................ 141

2.10.60 TSXMV0065 ................................................................................................................................ 141

2.10.61 TSXMV0066 ................................................................................................................................ 141

2.10.62 TSXMV0067 ................................................................................................................................ 142

2.10.63 TSXMV0068 ................................................................................................................................ 142

2.10.64 TSXMV0069 ................................................................................................................................ 142

2.10.65 TSXMV0070 ................................................................................................................................ 142

2.10.66 TSXMV0071 ................................................................................................................................ 143

2.10.67 TSXMV0072 ................................................................................................................................ 143

2.10.68 TSXMV0073 ................................................................................................................................ 143

2.11 z/Server Communicator (SOZCM) ................................................................................................ 143

2.11.1 SOZCM0001 ............................................................................................................................... 143

2.11.2 SOZCM0002 ............................................................................................................................... 144

2.11.3 SOZCM0003 ............................................................................................................................... 144

2.11.4 SOZCM0004 ............................................................................................................................... 144


Page: 15

2.11.5 SOZCM0005 ............................................................................................................................... 145

2.11.6 SOZCM0006 ............................................................................................................................... 145

2.11.7 SOZCM0007 ............................................................................................................................... 145

2.11.8 SOZCM0008 ............................................................................................................................... 145

2.11.9 SOZCM0009 ............................................................................................................................... 146

2.11.10 SOZCM0010 ............................................................................................................................... 146

2.11.11 SOZCM0011 ............................................................................................................................... 146

2.11.12 SOZCM0012 ............................................................................................................................... 146

2.11.13 SOZCM0013 ............................................................................................................................... 147

2.11.14 SOZCM0014 ............................................................................................................................... 147

2.11.15 SOZCM0015 ............................................................................................................................... 147

2.11.16 SOZCM0016 ............................................................................................................................... 147

2.11.17 SOZCM0017 ............................................................................................................................... 148

2.11.18 SOZCM0018 ............................................................................................................................... 148

2.11.19 SOZCM0019 ............................................................................................................................... 148

2.11.20 SOZCM0020 ............................................................................................................................... 148

2.11.21 SOZCM0021 ............................................................................................................................... 149

2.11.22 SOZCM0022 ............................................................................................................................... 149

2.11.23 SOZCM0023 ............................................................................................................................... 149

2.11.24 SOZCM0024 ............................................................................................................................... 149

2.11.25 SOZCM0025 ............................................................................................................................... 150

2.11.26 SOZCM0026 ............................................................................................................................... 150

2.11.27 SOZCM0027 ............................................................................................................................... 150

2.11.28 SOZCM0028 ............................................................................................................................... 151

2.11.29 SOZCM0029 ............................................................................................................................... 151

2.12 z/Server ISPF Panel Support (TSIPS) ............................................................................................... 151

2.12.1 TSIPS0001 .................................................................................................................................... 151

2.12.2 TSIPS0002 .................................................................................................................................... 151

2.12.3 TSIPS0003 .................................................................................................................................... 152

2.12.4 TSIPS0004 .................................................................................................................................... 152

2.12.5 TSIPS0005 .................................................................................................................................... 152

2.12.6 TSIPS0006 .................................................................................................................................... 153

2.12.7 TSIPS0007 .................................................................................................................................... 153

2.12.8 TSIPS0008 .................................................................................................................................... 153


Page: 16

2.12.9 TSIPS0009 .................................................................................................................................... 153

2.12.10 TSIPS0010 .................................................................................................................................... 154

2.12.11 TSIPS0011 .................................................................................................................................... 154

2.12.12 TSIPS0012 .................................................................................................................................... 154

2.12.13 TSIPS0015 .................................................................................................................................... 155

2.12.14 TSIPS0016 .................................................................................................................................... 155

2.12.15 TSIPS0017 .................................................................................................................................... 155

2.12.16 TSIPS0018 .................................................................................................................................... 156

2.12.17 TSIPS0019 .................................................................................................................................... 156

2.12.18 TSIPS0020 .................................................................................................................................... 156

2.12.19 TSIPS0021 .................................................................................................................................... 157

3 Troubleshooting ........................................................................................ 158

3.1 General Problem Determination ..................................................................................................... 158

3.2 z/Explorer Problem Determination ................................................................................................ 159

3.3 Application Workflow Manager Problem Determination ......................................................... 159

3.3.1 Modelled Action Does Not Work ............................................................................................. 160

3.3.2 Element List is Not Created ........................................................................................................ 161

3.3.3 Tree View is Not Expandable ...................................................................................................... 161

3.3.4 Tree View Elements Do Not Have a Correct Label ............................................................. 162

3.3.5 Edit Action (Simple Remote Edit or Browse) Does Not Work Properly ........................ 162

3.4 General Problem Solving Suggestions............................................................................................. 162

3.4.1 Determine the original exception ............................................................................................... 163

3.4.2 Clear The Persistent Cache In The Workspace ..................................................................... 163

3.4.3 Deal With Code Page Problems ................................................................................................. 164

3.4.4 Workspace Out Of Sync .............................................................................................................. 164

3.5 Gathering Information for the Micro Focus SupportLine.......................................................... 164

4 Sample Error Situations .......................................................................... 167

4.1 z/Server Is Not Active ........................................................................................................................ 167

4.2 Connection To z/Server Is Interrupted ......................................................................................... 167

4.3 Connection Problem When Connection Is Active ..................................................................... 168

4.4 No RACF OMVS Segment ................................................................................................................ 168

4.5 Model Error: Wrong Program ID ................................................................................................... 169

4.6 Model Error: Wrong Panel Name ................................................................................................... 170


Page: 17

4.7 Error Situations in an Attached Tool ............................................................................................. 170

5 Known Issues ............................................................................................. 173

6 Bibliography............................................................................................... 175


Page: 18

1 Introduction

This guide is meant as a help for error situations that can be traced back to the Workflow Manager.

Generally, we distinguish between expected and unexpected error situations. For example, an

expected error situation would be one when the user enters an incorrect connection password.

Unexpected error situations can be grouped into situations that were foreseen by the software and

those that were not. For example, a foreseen error situation would be that the connection to the

remote system is broken, and an example of an unforeseen error situation would be a programming

error in the software.

Depending on the type of error, the user or system administrator has different sources for help to

deal with the situation.

For expected and unexpected but foreseen error situations, an error dialog in the Eclipse

Workbench is displayed; for example:

The information in the dialog box should enable a user to handle this type of problem.

If the error was reported by the underlying z/Server software, a z/Server message ID is displayed in

the dialog (in the example above this would be SLR0071E). The first three alphabetic characters of

the message ID define the z/Server facility that detected the error. The facility acronym is followed

by four digits in the message ID which represent the sequential message number within the messages

for this z/Server facility. A z/Server message ID ends with a character determining the severity of the

message (I: informational, W: warning, E: error, S: severe error).

In some situations the XML error message is returned in the original XML format, for example:


Page: 19

The values of the XML tags FACID, MSGNO and SEVERITY have to be concatenated to give the

z/Server message ID, in this case SLR0131E.

The mapping between message prefix and z/Server facility is as follows:

Message Prefix z/Server Facility

API Application programming interface (TCPIP)

BND IEWBND (Binder) interface

CSI Catalog search interface

DSC Holder task configuration

EMC Extended MCS interface

HLD Holder task interface

IPC Command task

JES Job entry subsystem interface

LIC License interface

MAL Email interface

REC Recovery exception handler

REX REXX command environment

SJB Started job interface

SLR TSO scheduler interface

SPR Standard pool routine


Page: 20

SRV Server interface

SSI Interface to z/OS SSI

STA Started task interface

TAU Eclipse client interface

UNI Unicode conversion services

XML XML system parser interface

Detailed information about z/Server messages and how to handle them can be found in the z/Server

Messages book.

For unexpected but foreseen error situations, the exception caught is displayed in the text area

which is shown when the Details>> button is pressed.

The exception type often gives a hint what caused the problem. In the example above there is some

kind of network connection problem, which could for example mean that the connection to the

network was interrupted or that z/Server is not up and running.

If the information found in the error dialog is not sufficient to solve the problem, view the error log

for further information. Refer to chapter 3Troubleshooting for details on how to access the error

log, how to enrich it with debug information, and how to send that information to the Micro Focus

SupportLine.

Unexpected and unforeseen error situations will not normally produce an error dialog, but in some

cases, information related to a software exception not caught is recorded in the error log.

Chapter 2Error Messages lists all messages and describes the user, workflow modeller or server

administrator response. Chapter 3Troubleshooting contains instructions for the Application

Workflow Modeller (the administrator) on how to find the cause of problems that may have stem

from Application Workflow Modeller and offers solutions. It also describes the information that


Page: 21

Micro Focus SupportLine needs when the Application Workflow Modeller cannot solve the

problem.

Chapter 4Sample Error Situations is designed for support engineers to get accustomed to the way

the software reacts during selected error situations.

Chapter 5Known Issues shows currently known software errors, including tips on how to deal with

them.


Page: 22

2 Error Messages

The following user roles are used in this chapter:

User

Person who works with the Application Workflow Manager (AWM) software.

Model administrator

Person who maintains the Application Workflow model and develops tools for it.

Server administrator

Person who administrates the server which provides the services requested by the

Application Workflow Manager client.

Error messages have an ID consisting of nine alpha-numeric characters. The first five alphabetic

characters determine the internal package in which the error has arisen. The four following digits

represent a sequential numbering of the messages within the corresponding package.

Numbers in curly brackets within the message text represent placeholder, which are substituted by

variables during execution time, e.g. {0}.

Failed to read the parameter file {0} .

2.1 TAURUS Core (TSCOR)

2.1.1 TSCOR0001

An error occurred during execution of tool {0} or reading its output.

Explanation:

This exception can occur if a "job after action" encounters a problem while reading the tool output

from the executed job. This is a top-level exception which most probably contains more information

in the error details.

User response:

- Refresh the Job View to see if the corresponding job still exists. If it disappears after refreshing, the

tool output has probably been deleted already.

Model administrator response:

- Verify that the executed tool returns correct output.

- Verify that the tool output has been created properly (done by the REXX procedure TAUTOIFA).

2.1.2 TSCOR0002

Failed to read the parameter file {0} .


Page: 23

Explanation:

This exception can occur if a "job after action" fails to read the tool output from the executed job.

User response:

- Refresh the Job View to see if the corresponding job still exists. If it disappears after refreshing, the

tool output has probably been deleted already.


- Verify that the tool output has been created properly (done by the REXX procedure TAUTOIFA).

2.1.3 TSCOR0003

Error during execution of tool {0} .

Explanation:

This is a top-level exception that occurs if any executed tool (defined by a Tool Descriptor)

encounters a problem. A more detailed message can most probably be found in the error details

(usually a message created by the executed tool).

Possible reasons are:

- An individual error message was created by the executed tool. This depends on the tool type.

- An integrated tool encountered a problem.

- The modelled tool type could not be resolved.

- An executed tool did not return a valid tool execution status


Solve the cause of the exception if a detailed message can be found in the error details. If necessary

contact customer support.

2.1.4 TSCOR0004

The tool {0} exceeded the maximum return code of {1} .

Explanation:

This is a very common top-level exception. It occurs if any modelled tool returns a return code

which is higher than the modelled "Max_RC", which is an attribute of the "Application Options" ("4"

by default). A tool which returned a high return code most probably also returned a reason

message. The reason message should be visible under "Reason" in the error dialog or can be found

in the error details.

User response:

Contact the model administrator if the reason message of the executed tool is not clear or if there

is no reason message at all.


Page: 24

2.1.5 TSCOR0005

Failed to create the elementlist {0} .

Explanation:

An Action Descriptor with a reference to an Element List Structure (attribute "Has_Elementlist")

was executed but the creation of the Element list failed. This is a top-level exception, a more

detailed message can probably be found in the error details.

Possible causes:

- The action was not intended to create an Element list.

- The Element list cache cannot be saved in the workspace.

- Modelling errors.

Model administrator Response:

- If no Element list should be created by the corresponding action, remove the value of the

"Has_Elementlist" attribute from the Action Descriptor.

- See chapter "Element List is Not Created" to fix possible model problems.

2.1.6 TSCOR0007

A resource with the logical name {0} was not found.

Explanation:

A "Action Descriptor has Tool" relationship was defined with an "Affected_Resource" name but no

previous executed tool returned a logical resource name within a tool-defined resource operation.


- Correct the affected resource name in the "Action Descriptor has Tool" relationship or in the

output of the executed tool. Remove the attribute from the relationship if it was not intended to be

used.

- Verify that a tool which returns the logical resource name is executed before the tool which

returns the error message.

2.1.7 TSCOR0008

A Tool Type is missing for Tool Descriptor {0}

Explanation:

A Tool Descriptor was defined without a "Tool_Type" attribute.


Define a "Tool_Type" or "Integrated_Tool" attribute for the corresponding Tool Descriptor.


Page: 25

2.1.8 TSCOR0009

The tool {0} did not return a Tool Execution Status

Explanation:

An executed tool did not return a "Tool Execution Status" which is a Java class that belongs to the

API.


If a tool was executed by a custom created Tool Executor by using the product API contact the

corresponding programmer.

If necessary, contact customer support.

2.1.9 TSCOR0010

Tool Descriptor {0} needs an ISAPlugIn attribute, because its tool-type attribute was set to {1} .

Explanation:

A Tool Descriptor was modelled with a certain tool type which requires an "ISA_Plug-In" attribute

but it is missing. This is a modelling error.


Add an "ISA_Plug-In" attribute to the Tool Descriptor ("New Child" -> "ISA Plug-In") and define the

missing attributes. Example: If an input dialog was modelled (tool type "SWTDIALOG") it is required

to specify a plug-in ID in the ISA Plug-In attribute.

2.1.10 TSCOR0011

A bundle (Plug-In) with the ID {0} was not found.

Explanation:

A Tool Descriptor was modelled with an "ISPA_Plug-In" attribute where a certain plug-in ID was

defined but no plug-in with the specified ID was found. Either the plug-in ID is not correct or the

plug-in is not installed in the Eclipse environment.


Correct the plug-in ID in the "ISA_Plug-In" attribute of the Tool Descriptor or install the required

plug-in. The "Plug-In Registry" Eclipse View is useful to find installed plug-ins.

2.1.11 TSCOR0012

Activator for Plug-In {0} not found.


Page: 26

Explanation:

A Tool Descriptor was modelled with the tool type "PLUGIN" but the referenced plug-in does not

have an activator. This problem can only occur if additional plug-ins were implemented by using the

product API.


- Declare the class which implements the "IToolExecutor" interface to be the activator of the plug-

in.

2.1.12 TSCOR0013

No extension was found for the tool-type {0} .

Explanation:

The tool type of a modelled Tool Descriptor could not be resolved. Either the "Tool_Type"

attribute of the Tool Descriptor is incorrect or the plug-in which can execute the specified tool type

is not installed properly.


Correct the "Tool_Type" attribute of the corresponding Tool Descriptor or install the required

plug-in which contains a tool executor for the specified tool type.

2.1.13 TSCOR0014

Tool {0} returns less parameters than expected. {1} parameters were parsed while {2} parameters

were specified for this tool!

Explanation:

The number of parameters an executed tool returned was lower than the number of output

parameters modelled in its corresponding Tool Descriptor.


- Remove output parameters from the Tool Descriptor or let the tool return less values.

- If the number of returned values seems to be correct, verify that the output parameter separator

does not occur within the output values. Change the separator if necessary.

2.1.14 TSCOR0019

The FileDescriptor parameter pFDSource must not be null

Explanation:

The input file parameter for a tool creating a temporary file (remote edit, remote browse...) could


Page: 27

not be found. This can be caused by a modelling error or incorrect usage of the API.


- If the problem is caused by a modelled integrated tool verify that the input parameters are

correctly modelled.

2.1.15 TSCOR0024

Failed to execute local syntax check because the element cannot be determined.

Explanation:

A local syntax check could not be performed because no Element was found within the execution

context of the action.


Verify that actions containing a local syntax check integrated tool can only be executed on Elements

(no Global Actions).

2.1.16 TSCOR0025

Failed to execute local syntax check. There may be no Property Group associated with the Element.

Explanation:

A local syntax check failed because no Property with the attribute "Special_Property =

Property_Group" was associated to the selected Element.


Verify that a Property with the attribute "Special_Property" set to "Property_Group" is defined and

associated to the corresponding Element Type.

2.1.17 TSCOR0026

The local syntax check could not be performed because a local copy of the Element was not found.

Explanation:

A local syntax check can only be perfomed if a local copy of an Element exists. The local copy must

be created by the integrated tool "LocalFileCreator".

User response:

If a local copy of the Element must be created in a separate action (e.g. a modelled "Check-Out"

action), execute the action and retry the local syntax check. If you are working with different

workspaces, verify that the local copy was not created in a different workspace.


Page: 28


Define the integrated tool "LocalFileCreator" in the model and verify that the local syntax check

cannot be executed without the local file creator running beforehand.

2.1.18 TSCOR0030

Failed to receive an element with ID {0} .

Explanation:

An error occurred trying to get an element with its ID due to.

- The internal application folder cannot be found or created or is out of synchronisation

- The element XML file is damaged or cannot be parsed.

User response:

- Refresh the internal project folder

- Restart the client

- Clear the element and elementlist cache.

2.1.19 TSCOR0031

Failed to load a cached element list.

Explanation:

An error occurred when parsing the XML file containing the elementlist. Thereby an element could

not be determined with its ID.

- The internal application folder cannot be found or created or is out of synchronisation.

- The element XML file is damaged or cannot be parsed.

User response:

- Refresh the internal project folder.

- Restart the client.

- Clear the element and elementlist cache.

2.1.20 TSCOR0032

Illegal Property count after sorting Properties of File Descriptor {0} . Please check the sequence

numbers of the File Descriptor Properties.

Explanation:

Some sequence numbers properties of the file description that return the element list are not

correct


Page: 29


Check the sequence numbers for the properties of the file descriptor that return the element list

2.1.21 TSCOR0033

Failed to determine Element Types for Elementlist creation. {0}{1}

Explanation:

By trying to fill the element list, its element types

could not be determined in the file descriptor properties


Verify that the element types are configured under the properties of the file descriptor that create

the element list.

2.1.22 TSCOR0034

Failed to generate an Element ID. {0}{1}

Explanation:

By filling the element list, an element ID could not be generate


Ensure that the all the ID definitions and element type properties are return from the file descriptor

that create the element list

2.1.23 TSCOR0035

The Element Type {0} is not defined in the model.

Explanation:

By tying to fill the element list, an element typ could not be determine


- Verify that the element types are configured under the file description properties

- Ensure that the element list file return the element type at the correct position

2.1.24 TSCOR0036

Failed to determine an Element Type. Empty set of Properties was given.

Explanation:


Page: 30

This is a client code error

User Response:

Contact the customer support

2.1.25 TSCOR0037

Failed to load a cached filter.

Explanation:

The cached filters in the xml file cannot be read or the application folder is asynchronous.

User response:

- Refresh the internal application folder

- Restart the client

- Clear the filter cache

2.1.26 TSCOR0040

Failed to get file contents for job submit. File: {0}

Explanation:

The integrated tool "SubmitJCL" could not submit a job because the input JCL which is passed by a

File Descriptor could not be read. The file path that was used is returned at the end of this message.


- Verify why the file was not found under the given path or could not be read.

- If the submit tool was modelled within an editor action (Global Action), remove the file input

parameter from the corresponding Tool Descriptor. This will cause the tool to use the editor's

contents as JCL input.

- Check the troubleshooting chapter if the returned path appears to be empty.

2.1.27 TSCOR0041

Failed to retrieve a data stream for the job submit. Neither a file input parameter was configured

nor a valid editor is opened in the foreground.

Explanation:

No JCL input was found to submit a job.


Define the integrated tool "SubmitJCL" in one of two ways:


Page: 31

- Model a file input parameter which defines the JCL that should be submitted.

- Define an editor action (Global Action) for the submit action. The job can then be submitted from

an opened editor containing JCL.

2.1.28 TSCOR0042

Could not perform error feedback. The corresponding Element could not be retrieved.

Explanation:

The integrated tool "ErrorFeedback" was executed without an Element in the execution context.

This can occur if the tool is modelled within a Global Action.


Ensure that the integrated tool "ErrorFeedback" is not used in a Global Action. Model "Element

Type has Action" relationships as an alternative.

2.1.29 TSCOR0043

Invalid configuration of integrated tool RefreshDependencies: The integrated tool needs 2 file input

parameters. 1) Error Feedback XML 2) Copybooks XML.

Explanation:

The integrated tool "RefreshDependencies" was not modelled properly. Two file input parameters

are required.


Ensure that two file input parameters are modelled properly. The first referenced file must contain

compile errors and the second file must contain all required copy book entries.

2.1.30 TSCOR0044

Context missing for execution of integrated tool RefreshDependencies.

Explanation:

This is an internal client error that occurred during the execution of the integrated tool

"RefreshDependencies".


Contact customer support.


Page: 32

2.1.31 TSCOR0045

Element missing for execution of integrated tool RefreshDependencies.

Explanation:

This is an internal client error that occurred during the execution of the integrated tool

"RefreshDependencies".



2.1.32 TSCOR0046

Failed to refresh dependencies because a local copy of the Element was not found.

Explanation:

The "RefreshDependencies" tool can only be executed successfully if a local copy of an Element

exists. The local copy must be created by the integrated tool "LocalFileCreator".

User response:

- If a local copy of the Element must be created in a separate action (e.g. a modelled "Check-Out"

action), execute the action and retry the action. If you are working with different workspaces, verify

that the local copy was not created in a different workspace.


- Define the integrated tool "LocalFileCreator" in the model and verify that the

"RefreshDependencies" tool cannot be executed without the local file creator running beforehand.

2.1.33 TSCOR0047

The configuration of integrated tool {0} must contain a file output parameter.

Explanation:

The integrated tool "LocalTempFileCreator" was not properly modlled. It requires a file output

parameter which will be used to set the name of the created file for other tools to use.


Add a file output parameter to the Tool Descriptor of the integrated tool "LocalTempFileCreator".

2.1.34 TSCOR0048

Property sets are note supported by this product variant.


Page: 33

Explanation:

Property sets are currently only supported in combination with other products and reserved for

future use.


Contact customer support for more information about property sets and future plans.

2.1.35 TSCOR0049

At least three input parameters must be defined for the Itegrated Tool Property Group Creator: {0}

1) Property Set Name{0} 2) Language{0} 3) SYSLIB Path

Explanation:

The Integrated tool "PropertySetCreator" was not properly modelled (parameters missing). It

requires at least three input parameters:

1. Property Set name

2. Programming language

3. Library path

Model administrator response

Correct any modelling errors concerning the Tool Descriptor for the integrated tool

"PropertySetCreator". Valid parameter constallations are documented in the administration guide.

2.1.36 TSCOR0050

{0} resource operation failed due to an exception

Explanation:

This is a top level exception that will be printed into the error log if any exception occurs during a

resource operation. A more detailed error message can most likely be found in the error details.


Check the error details for more information.

2.1.37 TSCOR0051

The input file descriptor must have the type MVSPO_MEMBER,MVSSEQ or WORKSPACE_FILE

Explanation:

The integrated tool "PropertySetAssociator" was not properly modelled. The "Type" attribute of the

File Descriptor which is referenced by a file input parameter must have one of the following values:

- MVS_PO_Member


Page: 34

- MVS_SEQ

- Workspace_File

Model administrator response

Change the "Type" attribute of the referenced File Descriptor to one of the supported values (see

description).

2.1.38 TSCOR0052

At least two input parameters must be defined for the Integrated Tool Property Group Associator:

{0} 1) Property Set Name{0} 2) (File) Data Set / Member

Explanation:

The integrated tool "PropertySetAssociator" was not properly modelled (missing parameters).


- Correct modelling errors concerning the Tool Descriptor for the "PropertySetAssociator"

integrated tool. Valid parameter constellations are documented in the administration guide.

2.1.39 TSCOR0054

At least one Input Parameter must be specified for the Integrated Tool Property Group Remover:

Explanation:

The integrated tool "PropertySetRemover" was not properly modelled (parameter missing).


- Correct modelling errors concerning the Tool Descriptor for the "PropertySetRemover"


2.1.40 TSCOR0055

The parameter {0} has not a boolean value: {1}

Explanation:

An integrated tool Tool Descriptor was modelled with a boolean input parameter but the parameter

value was not boolean.


Correct the parameter value or change the attributes "True_value" and "False_value" of the

corresponding Property.


Page: 35

2.1.41 TSCOR0056

Invalid master configuration format parameter: {0}

Explanation:

This is an internal error situation. It occurs when the master configuration reader is called with an

invalid format parameter.



2.1.42 TSCOR0057

Failed to parse a system reference from the given master configuration file: {0}{1}

Explanation:

The given master configuration (printed at the end of this message) was invalid.


- Validate your master configuration and correct any errors. The syntax is documented in the

administration guide.

- If another error message is printed at the end of the message instead of the master configuration

correct any errors that prevent the master configuration from being returned.

2.1.43 TSCOR0058

Internal master-configuration parser error. The line {0} does not contain the {1} -tag.

Explanation:

This error is caused if a line of a master configuration in FLAT format does not contain an expected

keyword.


Correct the corresponding line in the master configuration.

2.1.44 TSCOR0059

Exception occurred while executing OS command: {0}

Explanation:

This is a top level message which covers several exceptions that can occur while an operating system

command is executed:

- Operating system error messages (e.g. "Invalid command 'XYZ'").


Page: 36

- I/O exceptions while sending the command or reading the output.


- Enable the client trace and verify that the sent commands are valid.

- Check the error details and fix any operating system dependent problems.

2.1.45 TSCOR0060

Failed to parse the return code {0} .

Explanation:

The return code of the executed tool did not contain a valid numeric value.


Correct the return code output in the called tool.

2.1.46 TSCOR0061

Tool {0} returns less parameters than expected. {1} parameters were detected whereas {2}

parameters were specified for this tool.

Explanation:

An executed tool returned less parameter than modelled output parameters in the corresponding

Tool Descriptor.


- Either correct to tool output or the Tool Descriptor definition in the model so that the modelled

output parameters match the actual tool output.

2.1.47 TSCOR0062

UPDATE resource operation failed. No Properties found for updating.

Explanation:

The UPDATE resource operation failed because no Property values were returned by the

corresponding tool. If no Property values are returned then there is nothing to update.


- If the "Resource_Processing" attribute of the Tool Descriptor was set to UPDATE verify that the

called tool returns the values that should be updated and that the Tool Descriptor has modelled

output parmaters matching those values.

- If the "Resource_Processing" attribute of the Tool Descriptor was set to TOOL_DEFINED verify


Page: 37

that the output parameters with the type "Element" are modelled.

- If the tool was not intended to update Properties change the "Resource_Processing" attribute of

the Tool Descriptor to READ.

2.1.48 TSCOR0063

Failed to determine a target Element list for INSERT operation.

Explanation:

An INSERT resource operation could not be executed because no Element list was found in the

execution context. This can be caused if the tool was executed from a Global Action.


If the corresponding Tool Descriptor is referenced by a Global Action but also an Element-

/Elementlist action create a copy of the Tool Descriptor, set the "Resource_Processing" attribute of

the copy to READ and use it for Global Actions.

2.1.49 TSCOR0064

INSERT operation failed. No Element Type could be determined for the new Element.

Explanation:

This is caused if neither a Property with the "Special_Property" attribute set to "Element_Type" was

returned by the INSERT tool nor an Element was selected when the action was executed.


- Return the match name of the Element Type by the INSERT tool and model it as an output

parameter referencing an "Element_Type" Property.

2.1.50 TSCOR0065

INSERT-CHILD operation failed. Selected resource does not have a children-list or -action.

Explanation:

A tool was configured as having resource operation of type INSERT-CHILD. But the tool did not

return a list of children for the given resource or is part of an action which does not generate a

children element list.


Verify that all tools having resource operation of type INSERT-CHILD are part of an action which

have a Has_Elementlist relation.


Page: 38

2.1.51 TSCOR0066

Failed to retrieve an Element list for INSERT-CHILD resource operation.

Explanation:

This is a top level exception. A more detailed error message can most likely be found in the error

details.


Check the error details for more information.

2.1.52 TSCOR0067

Failed to restore the system reference {0} because the remote system {1} was not found.

Explanation:

A system reference which is associated with a remote system could not be restored, because the

associated remote system could not be determined.

User response:

- Verify that the associated remote system still exists and has not been renamed in the Remote

System View.

- Delete the system reference and let it be re-created by connecting to the remote system.

2.1.53 TSCOR0068

Failed to load the Application

Explanation:

An exception occurred when loading an application from the local copy. Most likely the local copy of

the application is corrupted.

User response:

Open the application file lying in the internal project folder with the model editor and validate it. If it

is corrupted, remove it from the internal project folder. Then the application model will be loaded

from the remote system again.

If necessary, contact the model administrator.




Page: 39

2.1.54 TSCOR0069

Failed to find an Extension for the ZConnector Extension Point.

Explanation:

The zOS functionality is integrated by the Eclipse extension point de.soforte.taurus.zconnector. An

exception occurred when searching for an extension for this Eclipse extension point.



2.1.55 TSCOR0070

No ZConnector Extension was found.

Explanation:

The zOS functionality is integrated by the Eclipse extension point de.soforte.taurus.zconnector. No

plug-in which extends this extension point could be found in the workbench.


If the extension point de.soforte.taurus.zconnector is extended by a customer own extension, verify

that the extension point name is spelled correctly in the plugin.xml.

Otherwise contact customer support.

2.1.56 TSCOR0071

Cant write on File Descriptor of type InputStream

Explanation:

The setContents method was called with a parameter of type input stream. It is not possible to

write on an input stream.


Verify your tool output parameters of type file descriptor. The type of a file descriptor that is a tool

output parameter may not be of type "InputStream".

2.1.57 TSCOR0072

The file {0} does not exist.

Explanation:

The file determined by the given path could not be found.


Page: 40


If the file path originates from a modelled file descriptor, verify that the value under the attribute

"Name Physical" is correct.

If the file path is a tool result, verify that the toll returns the correct file path.

2.1.58 TSCOR0073

{0} is not a valid format for a Master Configuration Parser.{1}

Explanation:

The function to parse a master configuration file is integrated by an Eclipse extension point. The

parser was initialised with an invalid file format. Supported file formats are XML or flat file.


If the master configuration parser is implemented by a customer own plug-in, verify that the parsed

is initialised by one of the valid file formats.


2.1.59 TSCOR0074

A newer AWM model version is available. {0} The application will now be updated.

Explanation:

The model administrator has delivered a newer model version of the application than the version

which is loaded locally in the user's workspace. This is a message informing the user that the newer

version of the model is loaded in its workspace.

User response:

This is an informational message; no user action necessary.

2.1.60 TSCOR0076

Pre-init failed.

Explanation:

An internal plug-in initialisation error occurred.




Page: 41

2.1.61 TSCOR0077

System name missing.

Explanation:

The creation of a system reference failed because no name for the system was given.

User response:

Verify that a name was specified under the field "Connection name" of the New Connection dialog.

2.1.62 TSCOR0078

ISystemImage missing.

Explanation:

An internal exception occurred because no instance of the ISystemImage type was passed to the

method.



2.1.63 TSCOR0079

The resource with the ID {0} could not be found.

Explanation:

The persistent cache in the user's workspace seems to be inconsistent. There is a reference in one

of the cache files to a resource which has not been reloaded from the element's cache file.

User response:

Use the "Clear cache..." dialog to re-initialise the persistent cache in the Eclipse workspace.

2.1.64 TSCOR0080

Failed to create an ID for Element Type {0} . The key Property {1} is missing.

Explanation:

The creation of an internal AWM element failed because at least one of the configured key

properties of the element's element type could not be determined.


- Verify that the corresponding file descriptor is modelled correctly. The file descriptor must at least


Page: 42

contain all key properties of the returned element type.

- Verify that the corresponding tool correctly returns values for all modelled key properties.

2.1.65 TSCOR0081

Missing Property Value ( {0} ) for Resource Operation.

Explanation:

The creation of an internal AWM element ID failed because no property value was provided for at

least one of the configured key properties of the element's element type.


- Verify that the corresponding file descriptor is modelled correctly. The file descriptor must at least

contain all key properties of the returned element type.

- Verify that the corresponding tool correctly returns values for all modelled key properties.

2.1.66 TSCOR0084

No valid extension found for the PropertyGroup Manager Extension Point

Explanation:

The integrated "Local Syntax Check" tool is not supported by the product variant.


- Contact customer support.

2.1.67 TSCOR0087

No valid Extension found for the Error Feedback Parser Extension Point

Explanation:

This is an internal program exception. The "Error Feedback" interface did not find a valid

implementation.



2.1.68 TSCOR0089

An I/O Error occurred while reading a file input stream.

Explanation:


Page: 43

An exception occurred during the attempt to read and parse a tool response. Possible reasons are:

- Network problems.

- Invalid API usage by third party plug-ins.

- An internal program exception.

User response:

Check your network connection.



2.1.69 TSCOR0090

An error occurred while creating/opening the Eclipse project {0} .

Explanation:

The internal project could not be create/open because the project/workspace is damage

User response:

If the project is already created, refresh it. If this does not solve the problem, close your workbench

and try again or clear your workspace.

2.1.70 TSCOR0091

Failed to create the AWM system folder in the Workspace.

Explanation:

The system folder could not be created in the internal project because the project/workspace is

damaged.

User response:



2.1.71 TSCOR0092

Failed to create the AWM application folder in the Workspace.

Explanation:

The application folder could not be created in the internal project because the project/workspace is

damaged.


Page: 44

User response:



2.1.72 TSCOR0093

Error when parsing input for table. Value for property {0} not found.

Explanation:

There is a file input parameter declared as input for a dialog table. At least one line of the file

content does not deliver a value for every property associated with the file descriptor.


Verify the output file of the tool delivering the content for the dialog table. Ensure that the tool

delivers at least as many values as properties are configured for the file descriptor.

2.1.73 TSCOR0094

File {0} does not exist

Explanation:

The local file with the given path could not be found on the user's workspace.


If the file's path was derived from a file descriptor in the model, verify that the value under the

attribute "Name Physical" is correct.

If the file path is returned by a modelled tool, verify that the tool returns the correct path name.

2.1.74 TSCOR0095

The file {0} does not exist.

Explanation:

A file was not found based on a File Descriptor with the attribute "Type" set to "Workspace_File".

Typical reasons are:

- The file is not located in the workspace ("Type" attribute is incorrect).

- The "Name_Physical" attribute value was not entered correctly.

- The file path is returned incorrectly by another tool.

- The file path is correct but the file simply does not exist.


- Correct any errors that might cause the problem.


Page: 45

2.1.75 TSCOR0096

The Master Configuration file was not found. It must either be located in: {0}{1} .xml or{2} .txt or a

Master Configuration Provider must be implemented (Eclipse Extension Point).

Explanation:

This is an internal program exception that can be caused by the attempt to read a local master

configuration file which cannot be located.



2.1.76 TSCOR0097

Invalid argument. Element Type must not be null.

Explanation:

The element type of an element could not be resolve by filling the element list or by perform a

resource processing "tool defined " (insert, update).


- Verify that the element types of the element list are configured under the properties of the file

descriptor that create the element list.

- Verify that the Tool descriptors ('TOOL_DEFINED' Resource Processing) that insert/update

element with new element type have an element type output parameter (Property with element

type as special parameter).

2.1.77 TSCOR0099

Wrong parameters for Integrated Tool FileUploader. Two file input parameters were expected

Explanation:

The integrated tool "FileUploader" was not modelled properly. It requires two file input parameters.


Verify that two file input parameters are modelled for the "FileUploader" Tool Descriptor. The first

one will be used as the source file while the second one will be the target for the transfer operation.

2.1.78 TSCOR0100

Failed to create the temp file. Input parameters missing.

Explanation:


Page: 46

The integrated tool "LocalTempFileCreator" was not properly modelled (input parameters missing).


- Correct modelling errors concerning the Tool Descriptor for the "LocalTempFileCreator"


2.1.79 TSCOR0102

Bad extension for Extension Point {0}

Explanation:

The functionality to provide a system reference is integrated by an Eclipse extension point. An

exception occurred when determining the Java class which extends this extension point.



2.1.80 TSCOR0103

Invalid License Checker extension. The referenced class is incompatible with ILicenseChecker: {0}

Explanation:

This is an internal program exception. It is caused if a license checker plug-in was defined in an

invalid way.

Model administrator:


2.1.81 TSCOR0104

Cached Elements (et_elements.xml) could not be recovered

Explanation:

Failed to load the cached elements in the element XML file.

Maybe the internal application folder is asynchronous or not exist or the element XML file is

damaged.

User response:


- Clear the element list and element caches

- Delete the internal application folder and load the application again


Page: 47

2.1.82 TSCOR0105

Elements could not be cached. Failed to save et_elements.xml.

Explanation:

Failed to save the elements in the element XML file.

Maybe the internal application folder is asynchronous or not exist or the element XML file is

damaged.

User response:


- Clear the element list and element caches


2.1.83 TSCOR0107

Failed to save the Element list into cache.

Explanation:

The element list could not be save in the elementlist XML file

Maybe the internal application folder is asynchronous or not exist or the element list XML file is

damaged.

User response:


- Clear all the element list cache

- Delete the internal application folder and restart the client

2.1.84 TSCOR0108

The local AWM application folder could not be located.

Explanation:

The internal application folder does not exist in the workspace. Maybe the internal project folder is

asynchronous or damaged.

User response:

- Refresh the internal project folder

- Restart the workbench

- Delete the internal project if it exist and load the application again


Page: 48

2.1.85 TSCOR0109

Failed to store the Element list in file li_ {0} .xml.

Explanation:

An element list could not be save in its corresponding XML file.

Maybe the internal application folder is asynchronous or not exists or the element list XML file is

damaged.

User response:




2.1.86 TSCOR0110

An Element list could not be restored: li_ {0} .xml.

Explanation:

An element list could not be load from its corresponding XML file.


damaged.

User response:




2.1.87 TSCOR0111

Cached Element lists (lm_elementlists.xml) could not be recovered.

Explanation:

An element list dependency could not be load from the element list XML file.


damaged.

User response:





Page: 49

2.1.88 TSCOR0112

An error occurred when trying to save the file lm_elementlists.xml

Explanation:

An element list dependency could not be save in the element list XML file.

Maybe the internal application folder is asynchronous or not exists or the element list xml file is

damaged.

User response:




2.1.89 TSCOR0113

File lm_elementlists.xml could not be deleted.

Explanation:

The element list file could not be deleted. This can have the following cause

- The internal application folder is asynchronous, not existent or damaged.

- The element list XML file is not existent or is damaged.

User response:

- Refresh the internal application folder.

- Clear all the element list cache.

- Delete the internal application folder and load the application again.

2.1.90 TSCOR0114

Failed to delete a cached Element list (LI_ {0} ).

Explanation:

An element list file could not be deleted. This can have the following cause


- The element list XML file is not existent or damaged.

User response:





Page: 50

2.1.91 TSCOR0115

Failed to delete unreferenced Elementlists

Explanation:

Some element list files for which no references exist in the element list XML file could not be delete.

This can have the following cause


- The element list XML file is not existent or damaged.

User response:




2.1.92 TSCOR0116

A Thread was interrupted while initializing the element lists

Explanation:

This is an internal program exception that can occur while a cached Element list is loaded.



2.1.93 TSCOR0117

Invalid argument. Element Type must not be null.

Explanation:

The Element type is needed to create a element list entry. If it fails this can have the following

reasons:

- The output file parameter configured by the tool that creates the element list does not return the

value of the element type property or the element type property is not configured as output file

parameter.

- A Tool defined Resource Prossessing that creates/updates elements does not return the value of

the configured element type.


- Verify that the output file parameter configured by the tool that creates the element list, is

configured correctly and returns the element type for each entry.

- Verify that Tool defined Resource Prossessing that creates/updates elements returns the value of

the configured element type.


Page: 51

2.1.94 TSCOR0118

Failed to interpret the Selection Count attribute of the Action Descriptor: {0}

Explanation:

The "Selection_Count" attribute of a modelled enabled condition does not contain a valid value.


Change the "Selection_Count" attribute value to be either numeric or "*" which means that the

action is enabled no matter how many elements are selected.

2.1.95 TSCOR0119

{0} is not a valid file name

Explanation:

During the parsing the Error Feedback XML file, it was noticed that some error file references do

not have the structure of z/OS partitioned data set name.


Verify that error file references contained in the Error Feedback XML file have the structure of z/OS

partitioned data set name.

2.1.96 TSCOR0121

Failed to load error entries from cache (er_errorFeedback.xml).

Explanation:

The error entries cannot be loaded from cache (er_errorFeedback.xml).

Maybe the internal application folder is asynchronous, not existent or the er_errorFeedback.xml is

damaged.

User response:


- Delete manually the file er_errorFeedback.xml while the application is not loaded.

- Delete the internal application folder and restart the client.

2.1.97 TSCOR0122

Failed to store error entries into cache (er_errorFeedback.xml).

Explanation:

The error entries cannot be saved in cache (er_errorFeedback.xml).


Page: 52

Maybe the internal application folder is asynchronous, not existent or the er_errorFeedback.xml is

damaged.

User response:


- Delete manually the file er_errorFeedback.xml while the application is not loaded.

- Delete the internal application folder and restart the client.

2.1.98 TSCOR0123

The File Descriptor with the ID {0} could not be found among previous output parameters.

Explanation:

A file input parameter was modelled with the attribute "Parameter_From" set to "Previous_Tool"

but the File Descriptor was never returned as an output parameter by a previous executed tool in

this action.


Either set the "Parameter_From" value of the file input parameter to "Context" or make sure that

the File Descriptor is returned as output parameter by a previous tool in the action sequence.

Setting the "Parameter_From" attribute to "Context" requires the File Descriptor to have a valid

"Name_Physical" attribute value.

2.1.99 TSCOR0124

The Property {0} was not found whithin the execution context.

Explanation:

A Tool Descriptor was modelled with an input parameter with the "Parameter_From" attribute set

to "Context" but the referenced Property is not available in the execution context.


Either change the model so that the Property will be in the execution context or set the

"Parameter_From" attribute of the input parameter to "Context". To see if a Property is in the

execution context the Properties View needs to be opened while an Element is selected.

2.1.100 TSCOR0125

The Property {0} was not found among previous output parameters.

Explanation:

An input parameter was modelled with the attribute "Parameter_From" set to "Previous_Tool" but


Page: 53

the Property was never returned as an output parameter by a previous executed tool in this action.


Either set the "Parameter_From" value of the input parameter to "Context" or make sure that the

Property is returned as an output parameter by a previous tool in the action sequence.

2.1.101 TSCOR0126

An error occurred while loading a AWM filter.

Explanation:

An exception occurred when loading the file with the persistently cached filter data from the

internal project folder in the workspace of the user.

User response:

See the message under "Reason:" in the message dialog.

If necessary, contact the administrator.


Check the error log for more information.

2.1.102 TSCOR0127

An error occurred when trying to create a SAX parser instance

Explanation:

An internal XML parser problem occurred when loading the filter data from the persistent cache in

the internal project folder of the user's workspace.



2.1.103 TSCOR0128

An error occurred while parsing ft_filters.xml.

Explanation:

An internal XML parser problem occurred when loading the filter data from the persistent cache in

the internal project folder of the user's workspace.


Page: 54

Administrator response:


2.1.104 TSCOR0129

An error occurred when trying to save the file filters.xml.

Explanation:

Each time a filter is created, deleted or changed the file which contains the filter data is written to

the persistent cache in the internal project folder of the user's workspace.

This write action failed.


- Verify that the user has the authority to write to the internal project folder.

- Check the error log for more information.

2.1.105 TSCOR0130

Exception occurred when trying to delete ft_filters.xml.

Explanation:

The deletion of the cached filter data in the internal project folder failed when requested within the

context of the Clear Cache dialog.


- Verify that the user has the authority to delete files from the internal project folder.


2.1.106 TSCOR0131

An error occurred when trying to load the file jt_jobs.xml.

Explanation:

When an application is loaded the job information of the application is reloaded from the persistent

cache in the internal project folder of the user's workspace. This reload failed.

User response:






Page: 55

2.1.107 TSCOR0132

Failed to load opened files

Explanation:

The local cache for opened editor sessions could not be read. This is either caused by a corrupt

cache or the Eclipse workspace being out of synchronization.


- Refresh the internal project folder (see "Workspace Out Of Sync").

- Clear the persistent cache (see "Clear The Persistent Cache In The Workspace").

2.1.108 TSCOR0133

Failed to load error entries

Explanation:

The local cache for error feedback entries could not be read. This is either caused by a corrupt

cache or the Eclipse workspace being out of synchronization.




2.1.109 TSCOR0134

Failed to load Jobs

Explanation:

The local cache for executed jobs could not be read. This is either caused by a corrupt cache or the

Eclipse workspace being out of synchronization.




2.1.110 TSCOR0136

Failed to remove cached Elements

Explanation:

The persistent cache for modelled Elements could not be deleted. This is probably caused by the


Page: 56

Eclipse workspace being out of sync.



- Clear the cache manually (see "Clear The Persistent Cache In The Workspace").

2.1.111 TSCOR0137

Failed to remove cached filters

Explanation:

The persistent cache for created filters could not be deleted. This is probably caused by the Eclipse

workspace being out of sync.



- Clear the cache manually (see "Clear The Persistent Cache In The Workspace").

2.1.112 TSCOR0138

Failed to save {0} .

Explanation:

The cache could not be saved persistently in the workspace. This is most probably caused by the

Eclipse workspace being out of synchronization with the file system.


- Refresh the internal project folder and restart the client (see "Workspace Out Of Sync").

2.1.113 TSCOR0139

Backup folder could not be created.

Explanation:

The first step of the application update is to back up the files which contain the persistently cached

data in the workspace. In this step the creation of the backup folder failed. This means the complete

application update action failed.


- Verify that the user has the authority to create a folder in the internal project folder.



Page: 57

2.1.114 TSCOR0140

Failed to copy the backup folder. {0} .

Explanation:

The first step of the application update is to back up the files which contain the persistently cached

data in the workspace. In this step the copy of the files to the backup folder failed. This means the

complete application update action failed.


- Verify that the user has the authority to write to the backup folder in the internal project folder.


2.1.115 TSCOR0141

Converting an outdated application model failed.

Explanation:

This is an internal program exception. An attempt to convert a possibly outdated model failed. A

model will be treated as outdated if syntax errors were detected while loading it.

Model administrator support:

Please contact customer support.

2.1.116 TSCOR0142

An error occurred while trying to read the configuration file: {0}

Explanation:

This error occurs if a model could not read. This can have following reasons:

- Network problems.

- Model does not exist under the configured path from the master configuration.

- User is not authorized to read the model file.

User response:



- Make sure that the Properties View is opened and select the application in the Tree View. The

Properties View now shows configured attributes of the application (defined in the master

configuration). Verify that the "Model Location" property has a correct value.

- Verify that the user has read access to the model file.


Page: 58

2.1.117 TSCOR0143

The configuration file {0} could not be found.

Explanation:

This error occurs if a model file could not be found locally (or in the local network).

User response:






- If the model file is located on the mainframe use the prefix "mvs:" for the model path definition

(attribute "conf:") in the master configuration (e.g. "mvs:hlq.models(mymodel)").


2.1.118 TSCOR0144

System could not create configuration dataset {0}

Explanation:

This is an internal program exception that occurs when a downloaded model could not be saved in

the workspace.


- Refresh your internal project folder (see "Workspace Out Of Sync").

2.1.119 TSCOR0145

An exception occured when while trying to close the configuration file. {0}

Explanation:

This is an internal program exception that occurs when a downloaded model could not be saved in

the workspace.


- Refresh your internal project folder (see "Workspace Out Of Sync").


Page: 59

2.1.120 TSCOR0146

The given input stream is null. Possible reason: The AWM configuration file from the master

configuration does not exist.

Explanation:

This is an internal Program exception. It can occur if a model could not be loaded correctly.






- Contact customer support.

2.1.121 TSCOR0147

A system reference for connection {0} already exists!

Explanation:

This is an internal program exception. It is caused by the attempt to create a system reference that

conflicts with an existing one.



2.1.122 TSCOR0148

Failed to add the system reference because no ISystemImage (remote system) given.

Explanation:

This is an internal program exception. It is caused when a system reference is registered without a

system reference (ISystemImage interface).



2.1.123 TSCOR0149

Failed to load system references

Explanation:

This error occurs if cached system reference cannot be recovered after a client restart. Possible


Page: 60

reasons are:

- A remote system connection associated with a system reference cannot be found. This is caused if

the remote system connection was renamed or deleted.

- The cache is corrupt.

User response:

- Execute the "Add system reference" function in the Tree View to recreate the system reference.

2.1.124 TSCOR0150

An error occurred when trying to create a SAX parser instance

Explanation:

This is an internal program exception. It is caused by a failed attempt to instantiate a Java XML

parser.



2.1.125 TSCOR0151

Failed to recover cached systems (st_systems.xml).

Explanation:

This exception is caused by a corrupt system reference cache file (bad XML syntax). A detailed

error message can most probably be found in the error details.


Open the cache file in a text- or XML editor to determine and correct the error. The file is named

"st_systems.xml" and is located in the internal project.


2.1.126 TSCOR0152

An error occurred when trying to save the file st_systems.xml.

Explanation:

This is an internal program exception that occurs when a system reference cannot be saved into

cache. This can be caused when the Eclipse workspace is out of synchronization.


Page: 61

User response:

Refresh the internal project folder (see "Workspace Out Of Sync").

2.1.127 TSCOR0153

Model update check failed. Either the Master Configuration could not be read or the update itself

failed.

Explanation:

This is a top-level exception which occurs if updating the model or checking for a new model

version fails. This can have several reasons, including:

- The master configuration, containing information about the newest model version, could not be

read.

- The user cancelled an "Enter Password" dialog which was required for reading the master

configuration.

- Loading a new model version failed

A more detailed message can most probably be found in the error details.

Note that the update-check will only happen once per Application and Eclipse session.

User response:

- Fix any problems which might prevent the master configuration from being read.

- The Application can be updated manually by refreshing the corresponding system reference in the

Tree View and selecting the "Update Application" action in the context menu of the application. If no

"Update Application" action is displayed, then there is no newer version available.


- Check the error details for the cause of this message and resolve the problem.

2.1.128 TSCOR0154

Failed to check for model update. The Application does not seem to be loaded.

Explanation:

This is an internal program exception. An attempt to update an application was made but the

application does not seem to be loaded correctly.




Page: 62

2.1.129 TSCOR0155

The model update was performed but the version numbers still dont match: {0} Master

Configuration version number: {1}{0} Model version number: {3}

Explanation:

This problem is caused by an invalid configuration of model version numbers. The version number of

an application defined in a master configuration is not equal to the version number of the model it

refers to. The version number of a model must be set under "Application Options" in the "Version"

attribute.


Correct the version numbers of the application in the master configuration and the model.

2.1.130 TSCOR0156

Missing location keyword in model path: {0} . {1}

Explanation:

A model location path ("conf" attribute in master configuration) did not contain a location keyword.

The location keyword is used to determine on which platform a model is stored (e.g. "local:",

"mvs:").


- Add a location keyword in front of the model location. Valid keywords are documented in the


Example: "Conf: local:C:\myModel.xml"

2.1.131 TSCOR0157

Wrong location keyword in model path: {0} . {1}

Explanation:

The location keyword of a configured model path in a master configuration is invalid.


Correct the location keyword in the master configuration. Valid keywords are documented in the


2.1.132 TSCOR0158

A file input parameter must be defined for the Integrated Tool LocalSyntaxCheck (the program

source that should should be checked).


Page: 63

Explanation:

A file input parameter for a "LocalSyntaxCheck" integrated tool is missing.


Ensure that a file input parameter is modelled for the integrated tool "LocalSyntaxCheck".

2.1.133 TSCOR0159

A file output parameter (type = Workspace File) must be defined for the Integrated Tool File

Locator.

Explanation:

The integrated tool "LocalFileLocator" requires a file output parameter which is missing in the Tool

Descriptor definition.


Add a file output parameter to the "LocalFileLocator" Tool Descriptor which references a File

Descriptor of the type "Workspace_File".

2.1.134 TSCOR0160

A file input parameter must be defined for the Integrated Tool EDIT_CLEANUP.

Explanation:

The integrated tool "Edito_Cleanup" was not properly modelled. It requires a file input parameter

which points to the file that should be deleted.


Add a file input parameter to the "Edit_Cleanup" Tool Descriptor.

2.1.135 TSCOR0161

A file input parameter (describing the error XML input) must be defined for the Integrated Tool

ErrorFeedback

Explanation:

The integrated tool "ErrorFeedback" was not properly modelled. It requires a file input parameter.


Add a file input parameter to the "ErrorFeedback" integrated tool. The referenced File Descriptor


Page: 64

must point to a file which contains compiling errors in XML format.

2.1.136 TSCOR0163

No input parameters configured for the integrated Tool Local File Creator.

Explanation:

The integrated tool "LocalFileCreator" was not modelled properly (parameters are missing).


- Correct modelling errors concerning the Tool Descriptor for the "LocalFileCreator" integrated

tool. Valid parameter constellations are documented in the administration guide.

2.1.137 TSCOR0164

LocalFileCreator: Failed to create a local file because no Element Type could be determined from

the given parameters.

Explanation:

The integrated tool "LocalFileCreator" was not modelled properly. No required Element Type for

the file creation could be determined based on the modelled parameters.


- Correct modelling errors concerning the Tool Descriptor for the "LocalFileCreator" integrated

tool. Valid parameter constellations are documented in the administration guide.

2.1.138 TSCOR0165

Physical name of File Descriptor {0} missing.

Explanation:

A file descriptor, to which content should be written, has no value declared in the attribute "Name

Physical".


Add a valid value to the attribute "Name Physical" of the given file descriptor in the model file.

2.1.139 TSCOR0166

Could not find a Property with the ID {0} . This is normal when the model has been changed and an

old cache is loaded.


Page: 65

Explanation:

Self-explanatory

User response:

- Clear the persistent cache by the Clear Cache... dialog and refresh all the element list in the table

view.

2.2 TAURUS For z/Server (TSZSV)

2.2.1 TSZSV0001

Data set {0} is migrated. Migration level is {1} .{2} {2} Do you wish to recall the data set?

Explanation:

This is an informational message indicating that the selected data set is in migrated status on the

remote system.

It has to be recalled before it can be used.

User response:

Answer the dialog.

2.2.2 TSZSV0002

Data set is migrated.

Explanation:

The selected data set is migrated. The requested action cannot be performed.

User response:

Use the context menu action Recall to recall the data set. Then repeat the requested action.

2.2.3 TSZSV0003

Exception when allocating data set: {0}

Explanation:

A tool execution needs a parameter file to be allocated on the remote system with the given name.

This allocation failed.


Page: 66

Server administrator response:

Check the z/Server logs and z/OS SYSLOG for more information.

2.2.4 TSZSV0004

IO exception during dialog processing.

Explanation:

An I/O exception occurred during the execution of an ISPF dialog process.




Check the z/Server logs for more information.

2.2.5 TSZSV0005

z/Server exception during dialog processing.

Explanation:

A z/Server exception occurred during the execution of an ISPF dialog process.





2.2.6 TSZSV0006

Data set migration exception during dialog processing.

Explanation:

An exception occurred during the execution of an ISPF dialog process because a requested data set

was migrated.

User response:

Recall the requested data set and retry the ISPF dialog execution.


Page: 67

2.2.7 TSZSV0007

XML parse exception during dialog processing.

Explanation:

An XML response from the z/Server could not be interpreted.





2.2.8 TSZSV0008

No UI Tool configured for {0}

Explanation:

The ISPF dialog process called a panel for which no tool was configured in the corresponding model

file. Each panel called in the ISPF application must have a tool with an ISA_ISPF_Panel relation with

attribute Panel Name set to the name of the ISPF panel.


Correct the tool definition in the model file.

2.2.9 TSZSV0009

z/Server parameter error: Parameter {0} not found in parameter memory.

Explanation:

A parameter which was expected to be found in the parameter memory was not found.


Verify the model file. Verify if the attribute "Parameter From" is set correctly.

2.2.10 TSZSV0010

Invalid parameter string received from z/Server: {0}

Explanation:

An unexpected message format was send from the z/Server to the client during the execution of an

ISPF dialog process.


Page: 68





2.2.11 TSZSV0011

z/Server parameter error: Value length missing for {0}

Explanation:

An unexpected message format was send from z/Server to the client during the execution of an ISPF

dialog process.



- Verify that the extension of the corresponding ISPF panel is correct (TAUPARMS entry).

- Verify that the panel field parameters of the corresponding tool are modelled correctly.



2.2.12 TSZSV0012

z/Server parameter error: Value length for {0} is not numeric.

Explanation:


dialog process.







2.2.13 TSZSV0013

z/Server parameter error: Value length too short for {0}

Explanation:


Page: 69


dialog process.







2.2.14 TSZSV0014

Error when parsing input for table. More table properties configured than delivered by the remote

tool (File Descriptor: {0} ).

Explanation:


dialog process with an ISPF table.

The remote tool sent less values than properties were configured for the corresponding file

descriptor.


- Verify that the extension of the corresponding ISPF panel is correct (TAUTABV entry).

- Verify that the properties of the corresponding file descriptor are modelled correctly.

2.2.15 TSZSV0015

Error when parsing input for table. Value for property {0} not found.

Explanation:



The value of a property was not send in the expected length.




2.2.16 TSZSV0016

Error when parsing input for table.


Page: 70

Explanation:






2.2.17 TSZSV0017

Failed to parse the response: {0}

Explanation:


dialog process.

An expected tool parameter could not be found in the response.







2.2.18 TSZSV0018

IO Exception during ISPF dialog processing.

Explanation:

An I/O exception occurred during the execution of an ISPF dialog process.





2.2.19 TSZSV0019

Exception during ISPF dialog processing.


Page: 71

Explanation:

An exception occurred during the execution of an ISPF dialog process.





2.2.20 TSZSV0020

Port {0} freed

Explanation:

This is an informational message indicating that the given port is released at the end of an ISPF dialog

process.

User response:

This is an informational message.

2.2.21 TSZSV0021

There are no z/OS systems defined. Please define a new connection first.

Explanation:

A z/OS connection must be defined before a system reference can be defined.

User response:

Define a z/OS connection in the Remote System View first.

2.2.22 TSZSV0022

Target Management initialization interrupted.

Explanation:

The initialization of the target management which is a prerequisite for AWM was interrupted during

Eclipse start up.

User response:

If there are consecutive error situations, restart Eclipse.


Page: 72

2.2.23 TSZSV0023

{0} is incompatible with {1}

Explanation:

An ISystemImage instance was loaded which is not compatible with the zSystemUtilities class.


If this is a customer own implementation of the ISystemImage, ensure that this implementation

complies with the IConnectorService interface.


2.2.24 TSZSV0025

The file type {0} is not supported by {1}

Explanation:

A file descriptor with a file type which is not supported by the zServer edit class was passed to the

integrated tool RemoteEdit.



2.3 TAURUS Subsystem MVS (TSMVS)

2.3.1 TSMVS0001

The parameter file {0} could not be created.

Explanation:

The MVS parameter file used to pass long parameters between client and mainframe, could not be

allocated.

Server administrator:

- Check if the user has write authority to the parameter file.

- Delete the parameter file if it already exists and ask the user to retry the action. It is possible that

the parameter file was allocated incorrectly.

2.3.2 TSMVS0002

A file input parameter must be set.


Page: 73

Explanation:

An integrated Tool Descriptor for edit or browse was modelled without a file input parameter

(which is required).


Add a file input parameter to the corresponding Tool Descriptor. Verify that a File Descriptor is

referenced by the "Target_ID_File" attribute of the input parameter and that the "Type" attribute is

set to "File".

2.3.3 TSMVS0003

File input parameters are not yet supported by the ISPF Tool Executor.

Explanation:

An ISPFCOMMAND Tool Descriptor was modelled with a file input parameter, which is currently

not supported.


Remove the corresponding file input parameter from the Tool Descriptor or check whether the

"Type" attribute of the parameter was accidentally set to "File".

2.3.4 TSMVS0005

Could not connect to z/OS.

Explanation:

An ISPFCOMMAND tool could not be executed because a z/OS connection could not be

established completely. (XXXX) this is either caused by a network problem or an issue while loading

a model while connecting.

User response:

- Check your network connection to the server.

- Check your server definition in the client (host name, port).


- Verify that the host server is up and running correctly.

- Check the error details. If the underlying error message correlates to an issue while loading a

model, please verify that the model under the specified location of the "zExpConf" attribute of the

master configuration exists, is accessible and valid. If no "zExpConf" attribute is defined in the master

configuration, an internal client error occurred.


Page: 74

2.3.5 TSMVS0006

The command \ {0} \ could not be sent.

Explanation:

A ISPFCOMMAND tool failed executing a TSO or server command. This can either be caused by

executing a REXX procedure, communicating with an ISPF panel (XXXX) or an inconsistent client

installation.

User response:




- Check the error details to see whether the error was caused by an inconsistent client installation.

If that is the case re-install the client on the corresponding machine.


- Check whether the error message was caused while an ISPF dialog was executed.

2.3.6 TSMVS0007

Could not write on file: {0}

Explanation:

An ISPFCOMMAND tool failed to write input parameters into the parameter file.

User response:




- Check whether the user has write rights on the parameter file.

- Delete the parameter file if it already exists and ask the user to retry the action. It is possible that

the parameter file was allocated incorrectly.

2.3.7 TSMVS0008

The parameter file {0} could not be read.

Explanation:


Page: 75

An ISPFCOMMAND tool failed to receive parameters from the parameter file after the remote

function was executed.

User response:



- Check if the parameter data set exists and can be read.

- Check if the user has RACF authority to read the parameter file data set.

2.3.8 TSMVS0009

Invalid input parameter configuration: Parameter From = {0}

Explanation:

The "Parameter_From" attribute of an input parameter of a ISPFCOMMAND Tool Descriptor was

set to an unsupported value.


Change the "Parameter_From" attribute of the corresponding input parameter either to "Context"

or "Previous_Tool".

2.3.9 TSMVS0010

Wrong format for returncode of tool {0} .{1}{2}

Explanation:

The called ISPFCOMMAND tool did not return a return code in the expected format. In most cases

the tool returned an (error) message instead, which will then be printed at the end of the message.


- Check whether the corresponding tool received the correct parameters from the client. This can

be done by debugging the remote tool itself or enabling the client trace. If the parameter values are

not as expected correct both Action Descriptor and Tool Descriptor definitions in the model.

- Debug the corresponding tool on the z/OS.

2.3.10 TSMVS0011

The returncode {0} of tool {1} exceeds the maximum returncode of {2} .

Explanation:


Page: 76

An ISPFCOMMAND tool returned a return code that is higher than the configured maximum return

code (Max_RC) configured in the model. In most cases the corresponding tool also returned a more

specific error message that is shown beneath this error message. This can be an expected error

situation depending on the called tool.


- Verify that the action executed by the user was valid. This depends on the application modelled.

Example: The attempt to delete a data set member that is in exclusive use by another user counts as

an invalid action.

- Check if the specific tool received the correct input parameters. If not, check both the Action and

Tool Descriptor definition in the model.

- Debug the ISPFCOMMAND tool.

2.3.11 TSMVS0012

Unexpected return code of tool {0} . The return code was {1}

Explanation:

The return code value of the executed ISPFCOMMAND tool was not numeric.


- Verify that the return code values of the specific tool are always numeric and are not led or

followed by any other characters.

2.3.12 TSMVS0013

Tool {0} returns less parameters than expected.{1} parameters were detected while{2}

parameters were specified for this tool.

Explanation:

An ISPFCOMMAND tool returned less parameters than defined in its corresponding Tool

Descriptor.


- Either correct to tool output or the Tool Descriptor definition in the model so that the modelled

output parameters match the actual tool output.

2.3.13 TSMVS0014

Failed to create the job. The {0} statement is expected before line {1} .

Explanation:


Page: 77

The client failed to parse the output of an ISPFCOMMAND tool which submitted a job or was

executed in batch because the "JOBPARM: {jobid} {jobname}" statement was missing or in the wrong

position.


The JOBPARM statement should be created by the TAUTOIFA REXX procedure shipped with the

product. If no customizations were made to that procedure, an internal error has occurred. Contact

customer support.

2.3.14 TSMVS0015

Failed to parse the out parameter DSN for job {0} : {1}

Explanation:


executed in batch because the JOBOUTPARMDSN statement was missing.


The JOBOUTPARMDSN statement should be created by the TAUTOIFA REXX procedure shipped

with the product. If no customizations were made to that procedure, an internal error has occurred.


2.3.15 TSMVS0016

Failed to parse Job ID and name: {0}

Explanation:


executed in batch because the "JOBPARM: {jobid} {jobname}" statement was either missing or

invalid.


The JOBPARM statement should be created by the TAUTOIFA REXX procedure shipped with the

product. If no customizations were made to that procedure, an internal error has occurred. Contact

customer support.

2.3.16 TSMVS0023

An error occurred while parsing the error feedback file.

Explanation:

A general error occurred while the integrated tool "ErrorFeedback" tried to parse the error


Page: 78

feedback XML file. This can have several reasons:

- General connection problem

- The given file is not a valid XML file

- The Java XML parser encountered an internal problem

User response:

- Check your connection to the remote system (if available). Note that the error feedback XML file

is not necessarily located on a remote system.


Verify that the file input parameter of the corresponding Tool Descriptor points to the correct XML

file.


Determine why the XML file seems to be invalid by debugging the tool which should create the XML

file.

2.3.17 TSMVS0024

Missing file name for File Descriptor {0}

Explanation:

A remote file could not be read because no file name was found for a modelled File Descriptor.


If the file name should be returned from a modelled tool, check why the file name was found in the

tool which caused the error message. In this case the "Parameter_From" attribute of the file input

parameter must be set to "Previous_Tool". The tool which returns the file name must be called

before the tool which requires the file name. If the file name should not have been returned by a

tool, the "Name_Physical" attribute of the File Descriptor needs to be defined in the model.

2.3.18 TSMVS0025

The file {0} contains less values than configured properties.

Explanation:

The parsed file contains fewer values per line than Properties defined in the corresponding File

Descriptor.


Either change the creation of the file (or the file itself if it is not created dynamically) or the

corresponding File Descriptor in the model so that the number of values per line match the


Page: 79

modelled Properties of the File Descriptor.

2.3.19 TSMVS0026

The given error feedback XML file could not be parsed because the PACKAGE element was not

found.

Explanation:

The given error feedback XML file for the integrated tool "ErrorFeedback" was invalid because no

"PACKAGE" element was found.


- Verify that the file input parameter of the corresponding Tool Descriptor points to the correct

XML file.

- Check why the XML file seems to be invalid by debugging the tool which creates the XML file.

2.4 TAURUS UI (TSUIN)

2.4.1 TSUIN0001

The file {0} has been changed\n\nDo you want to save your changes before performing a local

syntax check?

Explanation:

This is a confirmation dialog message.

User response:

Reply OK or Cancel.

2.4.2 TSUIN0002

Exception when trying to add a new filter

Explanation:

The new filter action failed with an exception.




Page: 80

2.4.3 TSUIN0003

Error opening view {0}

Explanation:

The filter view could not be opened.

User response:

Open the filter view from the Eclipse Menu Bar: Window --> Show View --> Team Developer Filter

View and retry.

2.4.4 TSUIN0004

Error resolving filter

Explanation:

The filter action failed with an exception.





2.4.5 TSUIN0005

Interruption resolving filter

Explanation:

The filter action was interrupted.

User response:

Retry the action.

2.4.6 TSUIN0006

Exception when trying to get resource {0} .

Explanation:

When an application is loaded, all files which were open at the time, when the application was

unloaded, will be re-opened in the editor based on the information in the cache.

For the given element the re-open failed because no entry could be found in the cache.


Page: 81

Most probably the cached information is inconsistent.

User response:

Remove the file ft_openfiles.xml from the application folder in the internal project folder. See

chapter Troubleshooting for more information on how to remove the cached information.

2.4.7 TSUIN0007

Failed to re-open an editor from the resource: {0}

Explanation:

When an application is loaded, all files which were open at the time when the application was

unloaded will be re-opened in the editor based on the information in the cache.

For the given element the re-open failed because no entry could be found in the cache.

Most probably the cached information is inconsistent.

The workspace may have been switched between unload and load of the application.

User response:

Remove the file ft_openfiles.xml from the application folder in the internal project folder. See

chapter Troubleshooting for more information on how to remove the cached information.

2.4.8 TSUIN0008

The output file {0} could not be opened.

Explanation:

Opening the given file in the editor failed.

User response:


2.4.9 TSUIN0009

Opening editor for file {0} was interrupted.

Explanation:

Opening the given file in the editor was interrupted.

User response:

Retry the action.


Page: 82

2.4.10 TSUIN0010

No AWM Application active. Please load one.

Explanation:

An output file was tried to open when no AWM application was loaded.

User response:

Load the corresponding AWM application and try the action again.

2.4.11 TSUIN0011

Failed to open the AWM project while allocating the output file.

Explanation:

The internal project folder could not be opened for the creation of an output file.

User response:






2.4.12 TSUIN0012

Could not open the editor.

Explanation:

An output file was attempted to be opened in the editor; but the editor cannot be opened.

User response:


If necessary contact the administrator.



2.4.13 TSUIN0013

Compare failed


Page: 83

Explanation:

An I/O exception occurred during the compare action reading the files to be compared.

User response:





2.4.14 TSUIN0014

Compare failed due to an I/O error.

Explanation:

An I/O exception occurred during the compare action reading the files to be compared.

User response:





2.4.15 TSUIN0016

Failed to execute the integrated tool EditOpener. The File Descriptor {0} must be a workspace file

descriptor.

Explanation:

The execution of the integrated tool EditOpener failed because the file descriptor was not declared

as type workspace file descriptor.


Verify the type of the file descriptor associated as input parameter with the integrated tool

EditOpener. The file descriptor must be of type Workspace_File.

2.4.16 TSUIN0017

File does not exist.

Explanation:


Page: 84

The file to be opened in the editor could not be found in the workspace at the expected path.

A possible cause is that the workspace was switched since the last edit of the file.



2.4.17 TSUIN0018

Failed to retrieve the editor (IEditorPart) for the opened file. Save- and close-operations will not

work properly. {0} If an external editor was opened, you should check your file associations (Eclipse

preferences).

Explanation:

The editor which should be used to open the selected file could not be determined. The

consequence is that save and close actions won't work properly.

Probably there is file association missing for this file's extension in the Eclipse preferences.

User response:

Verify that the file association is set correctly for the file's extension in the Eclipse preferences. If

not, add a file association for the extension.

Otherwise see the message under "Reason:" in the message dialog.




2.4.18 TSUIN0019

Interrupted exception while waiting for platform UI initialisation

Explanation:

The platform UI initialisation process was interrupted.

User response:

Retry the action.

2.4.19 TSUIN0021

Failed to find the local file for Element {0}

Explanation:

The file for the given element to be opened in the editor could not be found in the workspace at the

expected path.


Page: 85

The workspace may have been switched since the last edit of the file.



2.4.20 TSUIN0024

An error occurred when trying to load the file ft_openfiles.xml.

Explanation:

Files which are locally open when an application is unloaded are persistently stored in the workspace

file ft_openfiles.xml. This file could not be loaded when the application is loaded again.

The workspace may have been switched between unload and reload of the application.

User response:

If the files need not to be opened again, ignore the message.

Otherwise if the cause is a workspace switch, change back the workspace.

If this does not help see the message under "Reason:" in the message dialog.

If this does not help neither, contact the administrator.



2.4.21 TSUIN0025

An error occurred when trying to save the file ft_openfiles.xml.

Explanation:

All files which are locally open when an application is unloaded are persistently stored in the

workspace file ft_openfiles.xml. This file could not be saved in the workspace.

User response:





2.4.22 TSUIN0026

CoreException during Save Action

Explanation:


Page: 86

There was a save action modelled which was executed when a file was saved. This save action failed.





2.4.23 TSUIN0027

Failed to open the view with the ID {0}

Explanation:

The opening of one of the Team Developer views failed.



2.4.24 TSUIN0028

Active editor contents can only be obtained from ITextEditors.

Explanation:

An action tried to read the content of the active editor (e.g. an action using the editor content to

submit it as a job). This is only possible if the editor is a text editor.

User response:

If possible change the type of the edited file to a type which is opened with a text editor.

2.4.25 TSUIN0029

Failed to close open editors.

Explanation:

When the workbench is shut down all open remote AWM files are closed. This close failed.

User response:

Determine why the close of the files failed.

Ensure that close actions which were not executed are processed manually (e.g. unlock a member in

the SCM system).


Page: 87

2.4.26 TSUIN0030

Exception occurred when saving the element information.

Explanation:

When an application is unloaded or the Eclipse workbench is closed the AWM elements are stored

permanently in the workspace. This element's save action has failed.

When the element information cannot be saved, no element lists for this application can be restored

in the next Eclipse session.

User response:


If this doesn't help, contact the administrator.



2.4.27 TSUIN0031

Configuration error: The Tool Descriptor {0} needs a ISA PlugIn attribute, because its tool type is

{1}

Explanation:

The given tool which is configured as UI tool (SWTDIALOG) doesn't have an ISA_PlugIn relation

attribute.


Add the required ISA_PlugIn relation attribute to the given tool in the model file.

2.4.28 TSUIN0032

The plug-in ID {0} for Tool Descriptor {1} is invalid for the tool type {2} .

Explanation:

The given tool descriptor contains an invalid plug-in ID for the given tool type in the ISA_PlugIn

relation attribute.

Allowed plugin IDs for tools of tool type SWTDIALOG are "de.soforte.taurus.inputdialog" or

"de.soforte.taurus.outputdialog".


Correct the plug-in ID for the given tool in its ISA_PlugIn relation attribute.


Page: 88

2.4.29 TSUIN0033

Missing file input parameter for integrated tool EditOpener.

Explanation:

The integrated tool EditOpener needs an input parameter of type file. This input parameter is

missing.


Add the missing file input parameter to the integrated tool EditOpener.

2.4.30 TSUIN0034

The file input parameter for the EditOpener contains no physical name.

Explanation:

In the file input parameter for the integrated tool EditOpener the value for the attribute "physical

name" is missing.


Add the physical name in the file input parameter of the integrated tool EditOpener in the model

file.

2.4.31 TSUIN0035

The integrated tool FileCompare with the ID {0} must have exactly two file input parameter while

only {1} were found.

Explanation:

The integrated tool FileCompare must be modeled with exactly two file input parameters. There

were more or less file input parameters found for the integrated tool FileCompare.


Correct the input parameters for the integrated tool FileCompare in the model file.

2.4.32 TSUIN0036

The action has been interrupted.

Explanation:

The current action has been interrupted by the user.


Page: 89

User response:

Try the action again.

2.4.33 TSUIN0037

Failed to delete cached files.

Explanation:

The deletion of the file cache failed during the execution of the Clear Cache action for an

application.

User response:

- See the message under "Reason:" in the message dialog.

- See chapter Troubleshooting for more information on how to delete the cache.

2.4.34 TSUIN0038

Exception when trying to get the value for property {0}

Explanation:

The value for a property which is part of a table within a dialog could not be determined.



2.4.35 TSUIN0039

Please insert a filter name

Explanation:

A filter definition always needs a filter name. The filter name is left empty.

User response:

Enter a name for the filter.

2.4.36 TSUIN0040

Exception when trying to get the application folder.

Explanation:

The application folder within the internal project folder could not be determined.


Page: 90

User response:


See chapter Troubleshooting for more help.




2.4.37 TSUIN0041

Core Exception when trying to read the job card file.

Explanation:

The file which contains the user specific job card settings could not be read from the internal project

folder in the workspace.

User response:





2.4.38 TSUIN0042

IO Exception when trying to read the job card file.

Explanation:

The file which contains the user specific job card settings could not be read from the internal project

folder in the workspace.

User response:





2.4.39 TSUIN0043

Exception when trying to write the job card file.

Explanation:


Page: 91

The values gotten from the job card dialog could not be written to the file which contains the user

specific job card settings in the internal project folder in the workspace.

User response:





2.4.40 TSUIN0044

Core Exception when trying to write the job card file.

Explanation:



User response:





2.4.41 TSUIN0045

IO Exception when trying to write the job card file.

Explanation:



User response:





2.4.42 TSUIN0047

Failed to retrieve values for Property {0}


Page: 92

Explanation:

The retrieve tool for the given property failed.

User response:




Verify that the retrieve tool is correctly implemented and configured in the model file.


2.4.43 TSUIN0048

Failed to resolve dependent value references.

Explanation:

Property dependent values were modelled in the "Value_Keys" attribute of a Select_Value Property

but could not be resolved.


Verify that the Value_Keys of the corresponding Property are modelled correctly.

2.4.44 TSUIN0049

Error while reading the output file {0} .

Explanation:

A file destined for an output dialog could not be read.


- Verify that the corresponding tool executed before the output dialog returns the file name

correctly.

- Enable the client trace and verify that the returned file name is mapped to the correct file output

parameter.

- Verify that the user has read access to the file

2.4.45 TSUIN0050

Output file not found in parameter memory: {0}

Explanation:

A File Descriptor for a file output field (output dialog) was not found. This may be caused by a tool


Page: 93

executor which did not save an output parameter correctly into the parameter memory. This is an

internal problem if no custom tool executor (tool type) was used.



2.4.46 TSUIN0051

Unable to set a value for output field {0}

Explanation:

A Property for an output field (output dialog) was not found. This may be caused by a tool executor

which did not save an output parameter correctly into the parameter memory. This is an internal

problem if no custom tool executor (tool type) was used.



2.4.47 TSUIN0052

Input file for parameter {0} could not be retrieved.

Explanation:

A file input parameter with the attribute "Parameter_From = Previous_Tool" was modelled for an

Input Dialog but the File Descriptor was not found in the parameter memory.


- Verify that the action is modelled correctly (see chapter "Troubleshooting").

2.4.48 TSUIN0053

No Properties defined for File Descriptor {0}

Explanation:

A file input parameter was modelled for an input dialog which refers to a file descriptor with the

attribute "Structure = Table". There are no Properties defined for the file descriptor.


- Add "has Property" relationships to the corresponding File Descriptor or set its "Structure"

attribute to "Unstructured"


Page: 94

2.4.49 TSUIN0054

Input file for selection table was not found.

Explanation:

There is a file input parameter declared as input for a dialog table. The file with the content for the

table could not be determined.

This is probably a modelling error.


Verify that the according file descriptor has the correct type and optionally the correct physical

name.

See the paragraph about modelling problems in the chapter Troubleshooting for further helpful

hints.

2.4.50 TSUIN0055

Input file for selection table could not be read.

Explanation:

There is a file input parameter declared as input for a dialog table. The file with the content for the

table could not be read. Might be a modelling error.


Verify that the according file descriptor has the correct type and optionally the correct physical

name.

See the paragraph about modelling problems in the chapter Troubleshooting for further helpful

hints.

2.4.51 TSUIN0057

Value for property {0} not found.

Explanation:

There is a file input parameter declared as input for a dialog table. At least one line of the file

content does not deliver a value for every property associated with the file descriptor.


Verify the output file of the tool delivering the content for the dialog table. Ensure that the tool

delivers at least as many values as properties are configured for the file descriptor.


Page: 95

2.4.52 TSUIN0058

Missing attribute in Global Editor Action: Keyword

Explanation:

A global action with an ISA_Editor_Action relation defined in the model file has a

SelectionProppertyMapping relation assigned with ValueFrom set to SelectedKeyword. But the value

of the keyword is not set.


Set the value of the attribute Keyword in the global Editor Action's SelectionPropertyMapping

relation (e.g. COBOL-COPYBOOK).

2.4.53 TSUIN0059

Failed to parse key word for editor action.

Explanation:

There is a global action with an ISA_Editor_Action relation defined in the model file.

A SelectionPropertyMapping relation is assigned to this Editor Action with ValueFrom set to

SelectedKeyword. The value under the Keyword attribute in the SelectionPropertyMapping relation

has not the expected format.


Correct the value in the Keyword attribute of the SelectionPropertyMapping relation.

Correct values are: COBOL-COPYBOOK, COBOL-INCLUDE or PLI-INCLUDE.

2.4.54 TSUIN0060

Failed to save the column configurations

Explanation:

When an application is unloaded or the Eclipse workbench is closed the column settings for the

Table View are stored in the local workspace. This save action failed.

User response:






Page: 96

2.4.55 TSUIN0061

Failed to save the column configurations

Explanation:


Table View are stored in the local workspace. This save action failed.

User response:





2.4.56 TSUIN0062

Failed to load the column user settings.

Explanation:


Table View are stored in the local workspace. When the application is loaded again, the column

settings are restored from this saved file. The restore of the column settings failed.

User response:





2.4.57 TSUIN0063

Error resolving filter

Explanation:

The refresh button was pressed in the Table View on an element list created by a filter. This caused

the filter action to be called. The filter action failed.

User response:

Verify if there is a network problem.


If this doesn't help, contact the administrator.


Page: 97

2.4.58 TSUIN0064

Interruption exception resolving filter

Explanation:

The refresh button was pressed in the Table View on an element list created by a filter. This caused

the filter action to be called which was interrupted by the user.

User response:


2.4.59 TSUIN0065

Exception when trying to load system references

Explanation:

During the initialisation of the Element Table View the system references are loaded from the

permanent cache in the workspace. The load of the systems failed.

User response:





2.4.60 TSUIN0066

Failed to open the file {0}

Explanation:

When an entry in the Team Developer Error List View is double clicked, the corresponding source

member should be opened in the editor. The open of the file failed.

User response:

Verify that the Location and Resource entry in the Error List View point to the location of the

source member. If this is not the case, it might be an error in the error feedback tool. In this case

contact the administrator.


Verify that the error feedback tool returns the correct location of the source member.



Page: 98

2.4.61 TSUIN0067

Found a matching editor ( {0} ) but failed to open it.

Explanation:

An error feedback entry was double clicked which should open the editor for the corresponding

source file. The editor associated with the file type could be determined. But the open failed.

User response:

Verify if the correct file association is defined for the source member in the Eclipse preferences.





2.4.62 TSUIN0068

Failed to retrieve the physical file of editor {0}

Explanation:


source file. Opening of the editor failed.

User response:





2.4.63 TSUIN0069

Failed to set markers for the file {0}

Explanation:


source file and mark the syntax errors with editor markers. The setting of the editor markers failed.

User response:





Page: 99


2.4.64 TSUIN0070

An error occurred reloading the filters

Explanation:

When an application is loaded the filter information of the application is reloaded from the cache in

the workspace. This reload failed.

User response:





2.4.65 TSUIN0071

Exception removing a filter.

Explanation:

The remove action on a filter failed with an exception.

User response:





2.4.66 TSUIN0072

Error opening view {0}

Explanation:

When a filter is executed, the Element Table View is opened to display the result of the filter action.

The opening of the Element Table View failed.




Page: 100

2.4.67 TSUIN0073

Exception adding a new filter.

Explanation:

A filter which is defined by the user is added to the internal filter list. The new filter list is stored

into the user's cache in the workspace. This add filter action ended with an exception.

User response:





2.4.68 TSUIN0074

An error occurred saving the filters

Explanation:

When an application is unloaded or the Eclipse workbench is closed the filter information is stored

into the user's workspace. The save of the filters failed.

User response:





2.4.69 TSUIN0075

Exception loading system references.

Explanation:

During initialisation of the Element Table View the system references are loaded from the

permanent cache in the workspace. The load of the systems failed.

User response:





Page: 101


2.4.70 TSUIN0077

Exception when getting the AWM job list.

Explanation:

When the Job View is initiated the job list input is loaded from the cache in the workspace. This load

failed.

User response:





2.4.71 TSUIN0078

Exception getting the job parts

Explanation:

When the Go Into action is selected on a job in the Job View the parts of the job (DDs) are

retrieved from the remote system. This retrieve failed.

User response:


Check if the job still exists on the remote system.




2.4.72 TSUIN0079

No Extension found for job utility.

Explanation:

The job utility is integrated by the Eclipse extension point de.soforte.taurus.jobutil. No extension for

this extension point could be found.


If the job utilities are integrated by a customer extension, verify that the extension point id is spelled


Page: 102

correctly in the plugin.xml.


2.4.73 TSUIN0080

Exception browsing a job with the id {0}

Explanation:

An Exception occurred browsing the job with the given id.

User response:





2.4.74 TSUIN0081

Exception saving the AWM job information.

Explanation:

When an application is unloaded or the Eclipse workbench is closed the job information is stored

into the user's workspace. The save of the job information failed.

User response:





2.4.75 TSUIN0082

Exception getting the AWM job list.

Explanation:

When an application is loaded the job information of the application is reloaded from the cache in

the workspace. This reload failed.

User response:




Page: 103



2.4.76 TSUIN0083

Exception loading system references

Explanation:

During initialisation of the Job View the system references are loaded from the permanent cache in

the workspace. The load of the systems failed.

User response:





2.4.77 TSUIN0084

Exception synchronizing the job information.

Explanation:

The refresh action in the Team Developer Job View failed with an exception.

User response:

Verify if there is a network problem.





2.4.78 TSUIN0085

Exception browsing a job with the id

Explanation:

The browse of the given job failed.

User response:



Page: 104




2.4.79 TSUIN0086

Invalid object given: {0}

Explanation:

This is an internal exception. A message has been called with an object of invalid type.



2.4.80 TSUIN0087

Failed to get children for {0}

Explanation:

An exception occurred when a branch was expanded the Tree View.

User response:



Check the server logs for more information.

Validate that the modelled GetChildren action for the corresponding element type works correctly.

2.4.81 TSUIN0088

An error occurred while searching for AWM Applications

Explanation:

An exception occurred when a system reference was expanded the Tree View.

User response:



Check the server logs for more information.

Validate that the REXX TAULAPPL respectively TAUZCAPP works correctly.


Page: 105

2.4.82 TSUIN0089

The following tool messages were returned during the action:

Explanation:

This is a summary of all tool messages which were issued by one of the tools which were executed

when the last action was performed.

User response:

Check the tool responses.

2.4.83 TSUIN0090

No Extension found for job utility.

Explanation:

The job utility is integrated via an Eclipse extension point. No extension for this extension point was

found in the workbench.


If the job utility is integrated using a customer written extension verify that the extension point id

(de.soforte.taurus.jobutil) is correctly spelled in the extension definition.


2.4.84 TSUIN0091

Failed to delete cached jobs.

Explanation:

During the execution of the Clear Cache action for an application the deletion of the job cache

failed.

User response:

- See the message under "Reason:" in the message dialog.

- See chapter Troubleshooting for more information how to delete the cache.

2.5 TAURUS UI Views (TSUIV)

2.5.1 TSUIV0002

Failed to expand the system reference {0}


Page: 106

Explanation:

The expand state of a cached system reference could not be restored after the client was restarted.

This was most probably caused by a model update or an inconsistent model.

User response:

Restart the client to see if the error occurs a second time. If it does, delete and re-add the system

from the tree view.

2.5.2 TSUIV0003

Exception during back up of application {0} .

Explanation:

The backup action of your active application failed.

User response:

Backup the files of your active application manually.

2.5.3 TSUIV0004

Failed to create a system reference.

Explanation:

An exception occurred during the creation of a system reference. Since this is a top-level exception

more details are most likely to be found in the error details. Possible reasons are:

- The internal project has become asynchronous to Eclipse.

- The client installation is inconsistent (conflicting plug-ins).

- A master configuration could not be received or parsed.

User response:

- Open the Navigator view and refresh the internal project (right click -> "Refresh") and retry the

action.

- If the problem appears to be related to the remote system connection, verify your network

connection to the specific system and check your connection definition (host name, port)


- If the problem appears to be caused while the Master Configuration was parsed, verify the

configuration itself and correct any inconsistencies. Usually a more detailed message can then be

found among the error details.


- If the master configuration file is provided by a remote system, verify that the server is up and

running correctly. Verify that all customization steps from the server installation guide concerning


Page: 107

the location and customization of the Master Configuration file are done correctly.

2.5.4 TSUIV0005

Exception when trying to refresh the system

Explanation:

The system reference could not be refreshed properly meaning that the underlying applications

could not be updated by reading the corresponding master configuration. A more detailed exception

can most probably be found in the error details.

User response:

- If the target system is remote check your network connection and configuration in the client (host

name, port).


- Verify that the master configuration for the corresponding system is valid.


- If the master configuration file is provided by a remote system, verify that the server is up and

running correctly. Verify that all customization steps from the server installation guide concerning

the location and customization of the Master Configuration file are done correctly.

2.5.5 TSUIV0006

Failed to associate a remote system.

Explanation:

Associating a remote system to a local system reference failed. This is most probably caused by a

corrupt client installation (Eclipse plug-in problems).

User response:

Restart the client with the -clean option and retry the action.



2.5.6 TSUIV0007

An exception occurred while trying to retrieve the containers.

Explanation:

The tree view could not be restored to its previous state. This is most likely caused by corrupt


Page: 108

cache files or Eclipse being out of sync with the local file system.


- Refresh the internal project from the Navigator View and restart the client.

- Clear the cache manually in the Navigator View and restart the client.

If the problem still occurs, contact customer support.

2.5.7 TSUIV0008

An error occurred while storing the containers

Explanation:

The current state of the Tree View could not be saved into cache. The reason for this is most likely

Eclipse being out of sync with the local file system.



If the problem still occurs, contact customer support.

2.5.8 TSUIV0009

Failed to expand the system reference {0}

Explanation:

An internal error occurred while the Tree View was being refreshed.



2.5.9 TSUIV0010

Following AWM dialog processes are still running: {0}{1}{0} Please close these processes first.

Explanation:

Loading an application failed because certain processes are still being executed in the active

application

User response:

Close the cited processes and retry loading the application.


Page: 109

2.5.10 TSUIV0011

Exception occurred when trying to load the application

Explanation:

The selected application could not be loaded. A more accurate message can most likely be found in

the error details.

User response:

If the model for the application is located on a remote system:

- Check your network connection.

- Check the settings of the remote system connection (host name, port)

- Check if your code page settings (including file mappings) for the remote system connection are

correct


- Verify that the application was defined correctly in the master configuration.

- Verify that the model for the application is located under the defined path in the master

configuration.


- If the mode for the application is located on the remote system, verify that the user has read

access for that file.

2.6 TAURUS Meta Model (TSMDL)

2.6.1 TSMDL0001

AWM model conversion failed.

Explanation:

AWM was trying to convert a model that seems to be incompatible with the current version. It

failed due to an exception during the conversion.


Open the model in the model editor and press the "Details" button in the editor. A list will open up

within the editor containing detailed messages why the model is incompatible with AWM. Send this

information to customer support if necessary.

2.6.2 TSMDL0002

The converter could not detect the reason for the model incompatibility. Please check the Details

area after closing this message.


Page: 110

Explanation:

AWM was trying to convert a model that seems to be incompatible with the current version but

failed since no repairable incompatibilities were detected.


Open the model in the model editor and press the "Details" button in the editor. A list will open up

within the editor containing detailed messages why the model is incompatible with AWM. Send this

information to customer support if necessary.

2.7 TAURUS Meta Model Editor (TSMET)

2.7.1 TSMET0001

Model import failed

Explanation:

The model import action could not be executed. Possible reasons are:

- At least one of the two models is inconsistent.

- An internal error occurred during the import process.

User response:

Use the validate function to find out if both models on their own are consistent. Fix the models if

validation errors occur. If both models seem to be valid contact customer support.

2.7.2 TSMET0002

At least one given object must not be null.

Explanation:

This is an internal program exception which is not supposed to occur under any circumstances.



2.7.3 TSMET0003

An error occured during the drag and drop operation.

Explanation:




Page: 111


User response:

Use the validate function to find out if both models on their own are consistent. Fix the models if

validation errors occur. If both models seem to be valid contact customer support.

2.7.4 TSMET0004

Unable to execute {0} command.

Explanation:




User response:

Use the validate function to find out if both models are consistent. Fix the models if validation errors

occur. If both models seems to be valid contact customer support.

2.7.5 TSMET0006

Error creating nested text editor

Explanation:

The model editor could not be opened and initiated properly. This is an internal program exception.



2.8 zExplorer For z/Server (TSXZS)

2.8.1 TSXZS0001

Failed to load XML file containing default connections

Explanation:

The XML file containing default z/Server connection definitions could not be loaded properly. The

file is named "defaultZConnections.XML" and is located in the Eclipse root folder.


- Verify that the file can be read by the user.

- Open the file in an (XML) editor and correct any syntax errors.


Page: 112

- Delete the file if it is not required.

2.8.2 TSXZS0002

{0} is not a valid MVS resource name.

Explanation:

Failed to parse a data set name from the passed MVS resource name. This is an internal problem.



2.8.3 TSXZS0003

No File Descriptor found for Data Set list.

Explanation:

A data set list could not be created because the File Descriptor defining the list was not found. This

is an internal error that may have been caused by the zExplorer model not being loaded correctly.

User response:

- Retry the action.

- Reconnect and retry the action.


- Verify that the z/Server EXEC library (containing the TAUZCAPP procedure) is in the SYSEXEC

concatenation of the user server.

- If the zExplorer model was customized, determine the problem in the customized model. Contact

customer support if necessary.

2.8.4 TSXZS0004

Failed to decrypt the saved password for user {0}

Explanation:

Failed to decrypt a stored password. The password was stored, because the user has marked the

"Save password" check-box in the "Enter password" dialog.




Page: 113

2.8.5 TSXZS0005

Failed to save the password (encryption problem)

Explanation:

Failed to encrypt and save a password. The password was supposed to be saved because the user

had checked the "Save password" check-box in the "Enter password" dialog.



2.8.6 TSXZS0006

Connect to {0} :{1} was not successful.

Explanation:

The connection to the z/Server could not be established. This is a top-level exception, which means

that a more detailed error message can most probably be found in the error details.

Possible reasons are:

- Network problems (the host cannot be reached).

- RACF error (wrong password, user not authorized, etc.).

- User cancelled the "Enter password" dialog.

- z/Server problems.

- Problems while calling the TAUZCAPP procedure

User response:

- Check your network connection.

- Verify that a valid user name and password were entered.


- Verify that the z/Server is up and running.

- Check the z/Server log for more information.


- Verify that the TAUZCAPP REXX procedure properly returns a master configuration.

- Verify that the returned master configuration file is valid.

2.8.7 TSXZS0011

User selected Cancel on disconnect dialog

Explanation:

If a user tries to disconnect from the z/Server while MVS edit sessions are still open in the client, a

confirmation dialog will come up to warn the user that the editor(s) will be closed before


Page: 114

disconnecting. If a user selects "Cancel" in this dialog, the disconnect action will be aborted and this

message i written into the error log.

User response:

No user action is required since cancelling the disconnect action was probably intended. If not, close

any open (non-local) editor or disconnect again and press "OK" in the confirmation dialog. Unsaved

changes can still be changed (individual confirmation dialogs will open).

2.8.8 TSXZS0012

Failed to properly log off from {0} :{1} . You are now disconnected.

Explanation:

The client failed to properly disconnect from the z/Server. Possible reasons are:

- The network connection was interrupted.

- The user server ended abnormally and did not shut down.

- Open edit sessions could not be properly ended.

The connection is shown as "disconnected" in the Remote Systems View. It is possible to

(re)connect normally afterwards.


Determine what causes the problem. Check the z/Server logs for more information. Contact


2.8.9 TSXZS0015

Failed to stop the user server for process ID {0}

Explanation:

The user server for a running ISPF dialog could not be stopped. This can be caused by a network

problem. Another reason may be abnormal end of the associated user server.

User response:

Contact the server administrator to verify that no user servers are left running.

If the error occurs each time a disconnect from z/Server is executed, restart the client.


Stop any user server still running for this user ID after the user has disconnected.

2.8.10 TSXZS0016

Disconnect from system {0} failed.


Page: 115

Explanation:

The client failed to properly disconnect from the z/Server. Possible reasons are:

- The network connection was interrupted.

- The user server ended abnormally and did not shut down.

- Open edit sessions could not be properly ended.

The connection is shown as "disconnected" in the Remote Systems View. It is possible to

(re)connect normally afterwards.

User response:

If any remote edit sessions were active before disconnecting and could not be ended properly,

reconnect to the z/Server and use the Dequeue function on any of the affected files. If the problem

occurs frequently, contact the server administrator.


Determine what causes the problem. Check the z/Server logs for more information. Contact


2.8.11 TSXZS0018

Failed to parse attributes of resource {0} .

Explanation:

A z/Server LIST response (LISTDSI for data sets or LISTMEM for members) could not be parsed

properly. This message is issued for every data set or member that could not be created.


Look for distinctive features of the resources that could not be parsed or created (special

characters, attributes, etc.) and contact customer support.

2.8.12 TSXZS0022

Directory blocks not numeric for {0}

Explanation:

Failed to determine the number of directory blocks for a data set. This is an internal problem

involving REXX procedure TAUZCLDS.




Page: 116

2.8.13 TSXZS0023

List Data set error.

Explanation:

An internal error occurred while executing the REXX procedure TAUZCLDS or parsing its results.


Please contact customer support.

2.8.14 TSXZS0025

Element Name Property missing for Element Type {0}

Explanation:

No Element name Property was modelled for the Element Type in a zExplorer model. Either the

model is incomplete or it was not loaded correctly.

User response:

Reconnect to the z/Server and retry the action. Contact the model administrator if the problem still

occurs.


- Verify that the master configuration for the system contains the "zExpConf" statement. If it does,

verify that the referenced model is valid and configure an "Element_Name" Property for the Element

Type.

- If no customized zExplorer model is supposed to be used, remove the attribute "zExpConf" from

the master configuration (it is commented out by default).

2.8.15 TSXZS0026

Failed to generate an Element ID for Element {0}

Explanation:

An Element ID for a zExplorer Element Type could not be generated successfully. Either the model

is incomplete or it was not loaded properly.

User response:

Reconnect to the z/Server and retry the action. Contact the model administrator if the problem still

occurs.


- Verify that the master configuration for the specific system contains the "zExpConf" statement. If it

does, correct any problems concerning the ID Definitions of the Element Types.


Page: 117

- If no customized zExplorer model should be used, remove or comment out the "zExpConf"

attribute from the master configuration (commented out by default).

2.8.16 TSXZS0027

Only subclasses of MvsResource (MvsDataset, MvsDatasetMember) can be renamed.

Explanation:

This problem occurs if the zExplorer API was used incorrectly and should not occur unless the

zExplorer was customized by third party plug-ins.



2.8.17 TSXZS0028

Only subclasses of MvsResource (MvsDataset, MvsDatasetMember) can be refreshed.

Explanation:

This problem occurs if the zExplorer API was used incorrectly and should not occur unless the

zExplorer was customized by third party plug-ins.



2.8.18 TSXZS0029

Converting an outdated application model failed.

Explanation:

An internal error occurred while a possibly outdated model was being converted. The conversion

will be initiated as soon as the model loader detects syntax errors in the model.



2.8.19 TSXZS0030

Failed to load the AWM configuration file: {0} because it seems to be incompatible with your client

version.

Explanation:


Page: 118

A model could not be loaded or opened completely because it contains syntax errors. Even the

model conversion was not successful.

User response:

- Verify that all code page settings are correct (connection properties and file mappings).


- Open the model in the model editor and click the "Details" button next to the text box containing

an error message. All syntax problems of the loaded model are then listed, including where they

occur. Correct the problems manually by editing the model with a text- or XML editor.

2.8.20 TSXZS0031

Missing type in zExplorer model: {0}

Explanation:

An explicitly needed object from the internal z/Explorer model was not found. This may be caused

by incorrect customization of the internal model or by a failure to load the model.


If the zExplorer model was customized determine the problem in the customized model. Contact


2.8.21 TSXZS0032

{0} will be opened in read-only mode because non-displayable characters were detected.

Explanation:

The file to be opened in the editor contains characters that cannot be converted properly using the

indicated code page. Write protection is automatically be enabled since saving the file back on the

mainframe would corrupt its contents.

User response:

Verify that your code page settings (including file mappings) are correct, change them if necessary

and re-open the file in the editor.

2.8.22 TSXZS0033

File {0} does not exist.

Explanation:

An internal problem occurred while opening an MVS file in the editor. The file location is within the


Page: 119

workspace since a temporary copy of the host resource should have been copied there.


- Contact customer support

2.8.23 TSXZS0034

User selected Cancel on save editor dialog

Explanation:

If a user tries to disconnect from the z/Server while MVS edit sessions are still open in the client, a

confirmation dialog will warn the user that the editor(s) will be closed before disconnecting. If the

user selects 'OK' in this dialog and the editor(s) contain unsaved changes, individual dialogs will come

up for each editor, asking whether to save the changes or cancel the disconnect action. If a user

selects "Cancel" in one of these dialogs, this message is written to the error log.

User response:

No response required. If selecting 'Cancel' was not intended, the action (disconnecting from the

z/Server or closing Eclipse) can simply be repeated.

2.8.24 TSXZS0035

The file {0} could not be deleted.

Explanation:

This is an internal problem. It occurs if the temporary copy of the remote file could not be deleted

after the editor was closed.



2.8.25 TSXZS0036

Failed to save file mappings.

Explanation:

An internal error occurred while saving the file mappings into the local cache. This is most likely

caused by Eclipse being out of sync with the local file system.




Page: 120

If the problem recurs, contact customer support.

2.8.26 TSXZS0037

Failed to reload file mappings.

Explanation:

An internal error occurred while loading the file mappings from the local cache. This is most likely

caused by Eclipse being out of sync with the local file system.



If the problem recurs, contact customer support.

2.8.27 TSXZS0042

Failed to create a member list.

Explanation:

Failed to create a list of members for an MVS data set. This is an internal error which most likely

contains more information in the error details.


If the zExplorer model was customized determine the problem in the customized model. Contact


2.9 zExplorer Subsystem JES (TSXJE)

2.9.1 TSXJE0001

Job name is missing.

Explanation:

The job name is missing for at least one job in the XML response of z/Server for a job list request.




Page: 121

2.9.2 TSXJE0002

Job ID is missing.

Explanation:

The job ID is missing for at least one job in the XML response of z/Server for a job list request.



2.9.3 TSXJE0003

An error occured while searching for a custom JesAdapterFactory.

Explanation:

This is a top level exception that will be printed into the error log. A more detailed error message

can most likely be found in the error details.

User response:





2.9.4 TSXJE0004

Failed to cancel job {0}

Explanation:

The job with the given ID could not be canceled on the remote z/OS system.

User response:

Verify that the user has the authority to cancel this job.



2.9.5 TSXJE0005

Failed get contents of job {0}

Explanation:


Page: 122

The contents of the given job could not be read from the remote z/OS system.

User response:

Verify that the user has the authority to read this job's contents.

If yes, contact the administrator.



2.9.6 TSXJE0006

Failed to browse job {0}

Explanation:

The given job could not be read from the remote system.

User response:

Verify that the user has the authority to read this job's contents.




2.9.7 TSXJE0007

Failed to cancel the job {0}

Explanation:

The given job could not be cancelled on the remote system.

User response:

Verify that the user has the right to cancel this job.

2.9.8 TSXJE0008

Failed to get job parts.

Explanation:

The selected job's parts could not be read from the remote system.

User response:

Verify that the user has the authority to read this job's parts' content.


Page: 123




2.9.9 TSXJE0009

Failed to browse job {0}

Explanation:

The given job part's content could not be read from the remote system.

User response:

Verify that the user has the authority to read this job part's content.




2.9.10 TSXJE0010

Unexpected return value null from IJobFacility {0}

Explanation:

A NullPointer exception occurred determining the job facility class. This is an internal error.



2.9.11 TSXJE0011

Retrieving job information encountered a problem.

Explanation:

The job's meta information could not be read from the remote system.

User response:

Contact the administrator.




Page: 124

2.10 zExplorer Subsystem MVS (TSXMV)

2.10.1 TSXMV0001

An error occurred while searching for a custom MvsAdapterFactory.

Explanation:

The extension which extends the extension point

de.soforte.zexplorer.subsystem.mvs.CustomMvsAdapterFactory could not be loaded.



2.10.2 TSXMV0002

Changing password failed.

Explanation:

During the change password dialog an I/O exception occurred.

It may be caused by an encryption problem (might be a code page problem).


- Verify that a valid code page is set for the MVS Explorer settings.

- Verify that there is no network problem.




2.10.3 TSXMV0003

RECALL failed. The data set was not created.

Explanation:

The creation of a new MVS data set was executed on an existent data set. In this case the attributes

of the new data set are taken from the attributes of the selected data set. As the selected data set

was migrated, it has to be recalled at first. This recall failed which means that the new data set is not

allocated.

User response:

If possible select another data set as model data set for the data set creation.



Page: 125




2.10.4 TSXMV0004

Logoff failed

Explanation:

Logging off the user off from z/Server using the hidden command !LOGOFF failed.



2.10.5 TSXMV0005

Failed to set the debug parameter

Explanation:

The call to the REXX TAUZCDBG to set the debug parameter resulted in an I/O exception.


Verify that the z/Server EXEC library is in the SYSEXEC concatenation of the user server.


2.10.6 TSXMV0007

Failed to send the following HEX Characters: {0}{1}

Explanation:

A list of characters is shown that could not be sent to z/Server using the hidden command

!SENDHEX.

User response:


2.10.7 TSXMV0008

Sending hexes cancelled by user

Explanation:


Page: 126

The hidden action !SENDHEX was cancelled by the user.

User response:


2.10.8 TSXMV0009

Paste error.

Explanation:

The paste action for a z/OS data set failed.

User response:


2.10.9 TSXMV0010

Severe Paste error.

Explanation:

The paste action for a z/OS data set resulted in a severe error.

User response:







2.10.10 TSXMV0011

Severe error when trying to paste member list {0} from {1}

Explanation:

Pasting a list of z/OS partitioned members failed.

User response:




Page: 127





2.10.11 TSXMV0012

Severe error when trying to paste member {0} from {1}

Explanation:

Pasting a list of partitioned data set members failed.

User response:







2.10.12 TSXMV0013

Severe error when checking member existence of {0} in {1}

Explanation:

Pasting a member of a partitioned data set failed.

User response:




2.10.13 TSXMV0014


Explanation:


Page: 128

Pasting a list of z/OS partitioned members failed.

User response:




2.10.14 TSXMV0015

Data set allocation error.

Explanation:

The allocation of a z/OS data set failed.

User response:


2.10.15 TSXMV0016

Failed to create a backup for file {0}

Explanation:

The save of an edited file failed. The backup of the file which is written in this case also failed.

User response:

Temporarily save the changes in the editor so that they are not lost (e.g. by cutting/pasting the

editor contents into a temporary local file).

Determine why the edited file could not be saved.



2.10.16 TSXMV0017

Failed to save the member: {0} . A backup was made at: {1}

Explanation:

Saving an edited file failed. Therefore a backup of the file was written to the named path.

User response:

Determine why the save of the file failed.


Page: 129



2.10.17 TSXMV0018

Could not find any z/Server tool with ID {0}

Explanation:

There is no z/Server tool defined for the given tool ID.


If this is a custom z/Explorer model check the model definition and the plug-in code for the given

tool ID.


2.10.18 TSXMV0019

The z/Server Tool {0} needs at least one input parameter (data set name).

Explanation:

There was no input parameter defined for the tool although it needs at least one input parameter.


If this is a custom z/Explorer model check the model definition and the plug-in code for the given

tool ID.


2.10.19 TSXMV0020

The tool {0} needs exactly one input parameter (fully qualified data set or member name).

Explanation:

It was expected that exactly one input parameter was declared for the tool. The parameter was

missing or more than one input parameter was declared for the tool.


If this is a custom z/Explorer model check the model and the plug-in code for the given tool ID.



Page: 130

2.10.20 TSXMV0021

The z/Server Tool {0} needs exactly one input parameter (data set name).

Explanation:

It was expected that exactly one input parameter was declared for the tool. The parameter was

missing or more than one input parameter was declared for the tool.




2.10.21 TSXMV0022

The z/Server Tool {0} needs exactly one file output parameter ({1} ).

Explanation:

It was expected that exactly one file output parameter was declared for the tool. The parameter was

missing or more than one output parameter was declared for the tool.




2.10.22 TSXMV0023

Getting members of data set {0} failed with message: {1}{2}

Explanation:

The members of the given data set could not be retrieved from the remote z/OS system.

User response:

See the included z/Server messages for more details.

2.10.23 TSXMV0024

Invalid filter string.

Explanation:

An unsupported filter string was used. Unsupported filter strings are *, % or filter strings starting

with *.


Page: 131

User response:

Use a more qualifying filter string.

2.10.24 TSXMV0025

Failed to receive files for filter request: {0}

Explanation:

The filter request for the given filter string failed.





2.10.25 TSXMV0026

Getting data sets for filter string {0} failed with message: {1}{2}

Explanation:

The filter request for the given filter string failed.

User response:


2.10.26 TSXMV0027

At least one LISTDSI parser error occurred.

Explanation:

The parser analysing the response of the LISTDSI request to z/Server detected at least one error in

the response.

User response:


2.10.27 TSXMV0028

Failed to associate a Delta Visitor. SAVING WILL NOT WORK if youre in edit mode.

Explanation:


Page: 132

There is no delta visitor registered which is responsible for the save processing when an edited file is

saved.



2.10.28 TSXMV0029

Insert of member {0} failed.

Explanation:

Adding a member to a z/OS partitioned data set failed.

User response:


2.10.29 TSXMV0030

Failed to submit job. No z/OS job support was found (implementation of extension point {0} ).

Explanation:

The submit of a job failed.

Most likely there was no extension for the extension point de.soforte.zos.JobFacility found.



2.10.30 TSXMV0031

Failed to submit job.

Explanation:


User response:


If necessary contact the model administrator.




Page: 133

2.10.31 TSXMV0032

RECALL failed

Explanation:

The recall of a migrated data set failed.

User response:


2.10.32 TSXMV0035

Job submit failed. Failed to find a job support extension.

Explanation:

Submit of a job failed.

Most likely there was no extension for the extension point de.soforte.zos.JobFacility found.



2.10.33 TSXMV0036

Job submit failed.

Explanation:


User response:


If necessary contact the model administrator.



2.10.34 TSXMV0037

Delete error.

Explanation:

Deletion of a member of a z/OS partitioned data set failed.


Page: 134

User response:


2.10.35 TSXMV0038

Severe error when trying to duplicate a PO member {0}

Explanation:

The duplicate action for a member in a z/OS partitioned data set failed.

User response:


2.10.36 TSXMV0040

Failed to dequeue the resource {0}

Explanation:

The Dequeue action for a z/OS data set failed.

User response:







2.10.37 TSXMV0041


Explanation:

The paste action for a z/OS partitioned data set member list failed.

User response:



Page: 135

2.10.38 TSXMV0042

Severe error when checking for existence of member {0} in {1}

Explanation:

An exception occurred when checking if the given member exists in the given data set.

User response:







2.10.39 TSXMV0043


Explanation:

The paste action of a list of z/OS partitioned data set members failed.

User response:







2.10.40 TSXMV0044

Exception when trying to connect to {0}

Explanation:

The connection to the remote system did not work when the search action was called.

User response:

Check if there are any network problems.



Page: 136






2.10.41 TSXMV0045

There is no z connection defined. Please define a new connection first.

Explanation:

The z/Server search action was called without a z/Server connection defined in the Remote Systems

View.

User response:

Define a z/Server connection in the Remote System View. Then repeat the search action.

2.10.42 TSXMV0046

Invalid begin column specified

Explanation:

The parameter "Begin column" for the search has an invalid format. It must have numeric format.

User response:

Enter a numeric value in the input field "Begin column" or leave it empty.

2.10.43 TSXMV0047

Invalid end column specified

Explanation:

The parameter "End column" for the search has an invalid format. It must have numeric format.

User response:

Enter a numeric value in the input field "End column" or leave it empty.

2.10.44 TSXMV0048

No system was specified.


Page: 137

Explanation:

Access to the remote z/Server connection caused a NullPointer exception.



2.10.45 TSXMV0049

Error when setting markers for file {0} .

Explanation:

The search markers could not be set in the editor when a file was opened from the search result

view.

User response:





2.10.46 TSXMV0050

Failed to browse the file

Explanation:

Browsing a file from the Search Result View failed.

User response:





2.10.47 TSXMV0051

Remote code page does not contain a valid code page.

Explanation:

The code page entered under "Remote Code page" in the z/Server connection definition is not a


Page: 138

valid code page ID.

User response:

Choose a valid code page for the remote code page.

2.10.48 TSXMV0052

Local code page does not contain a valid code page.

Explanation:

The code page entered under "Local Code page" in the z/Server connection definition is not a valid

code page ID.

User response:

Choose a valid code page for the local code page (typically UTF-8).

2.10.49 TSXMV0054

Exception occurred during data set DragAndDrop action

Explanation:

The drag/drop action of a z/OS data set failed.

User response:


2.10.50 TSXMV0055

The source data set is migrated

Explanation:

A drag/drop could not be executed because the source data set is migrated.

User response:

Recall the migrated data set and retry the action.

2.10.51 TSXMV0056

Exception occurred during member DragAndDrop action

Explanation:


Page: 139

The drag/drop action of a member of a z/OS partitioned data set failed.

User response:


2.10.52 TSXMV0057

Get Bind Data failed.

Explanation:

The binder information for a z/OS load module could not be retrieved.

User response:


If necessary contact the server administrator.



2.10.53 TSXMV0058

Failed to browse the member {0}

Explanation:

Browsing of the given member of a z/OS data set failed.

User response:







2.10.54 TSXMV0059

The source data set is migrated

Explanation:

The source data set of a drag/drop action is migrated.


Page: 140

User response:

Recall the migrated data set. Retry the drag/drop action.

2.10.55 TSXMV0060

Delete error.

Explanation:

Deletion of a z/OS data set failed.

User response:


2.10.56 TSXMV0061

Exception occurred when calling search REXX TAUZCSRC

Explanation:

The call to the REXX TAUZCSRC failed.

User response:



Verify that the z/Server EXEC library is defined in the SYSEXEC concatenation of the z/Server user

server.

Verify that the z/Server EXEC library contains the REXX TAUZCSRC.


2.10.57 TSXMV0062

Dataset Migrated/Exception when calling search REXX TAUZCSRC

Explanation:

The data set to which the search was applied is migrated.

User response:

Recall the migrated data set and retry the search action.

2.10.58 TSXMV0063

Unexpected response from LOGOFF


Page: 141

Explanation:

The log off from the z/Server using the hidden command !LOGOFF results in a response from the

server that cannot be parsed.



2.10.59 TSXMV0064

CALLREXX Failed

Explanation:

The hidden command !CALLREXX results in a response from the server that can not be parsed.



2.10.60 TSXMV0065

Target member name must be different from source member name

Explanation:

The name chosen for the target member is identical to the name of the source member in the

duplicate action.

User response:

Choose a name for the target member different from the name of the source member.

2.10.61 TSXMV0066

Data set name must not contain blanks.

Explanation:

In the data set allocation dialog a data set name was entered which contains blanks. This is not

allowed for z/OS data sets.

User response:

Enter a data set name without blanks.


Page: 142

2.10.62 TSXMV0067

Please enter a value greater than zero as primary space amount.

Explanation:

In the data set allocation dialog a value of zero was entered for the primary space allocation.

User response:

Enter a value greater than zero as primary space allocation.

2.10.63 TSXMV0068

Please enter a numeric value as primary space amount.

Explanation:

In the data set allocation dialog a non-numeric value was entered as primary space allocation.

User response:

Enter a numeric value greater than zero as primary space allocation.

2.10.64 TSXMV0069

Please enter a numeric value as secondary space amount.

Explanation:

In the data set allocation dialog a non-numeric value was entered as secondary space allocation.

User response:

Enter a numeric value as secondary space allocation.

2.10.65 TSXMV0070

Please enter a numeric value for directory blocks.

Explanation:

In the data set allocation dialog a non-numeric value was entered as directory block amount.

User response:

Enter a numeric value for directory blocks.


Page: 143

2.10.66 TSXMV0071

Please enter a numeric value as record length.

Explanation:

In the data set allocation dialog a non-numeric value was entered as record length.

User response:

Enter a numeric value as record length.

2.10.67 TSXMV0072

Please enter a numeric value as block size.

Explanation:

In the data set allocation dialog a non-numeric value was entered as block size.

User response:

Enter a numeric value as block size.

2.10.68 TSXMV0073

Failed to get members of data set {0}

Explanation:

A top level exception occurred when determining the members of a z/OS partitioned data set.

User response:

See the message under "Reason:" in the message dialog. Maybe the user has not the authority to list

the members of the partitioned data set.


2.11 z/Server Communicator (SOZCM)

2.11.1 SOZCM0001

Internal file mappings error. The file mapping {0} was not found in the index.

Explanation:

The given file mapping could not be found in the internal file mapping cache.


Page: 144

User response:

If the file mapping is missing in the File Mappings View add it and retry the action.

Verify that the file file_mapping.xml file exists in the internal project folder in the user's workspace.

Restart Eclipse to see if the file mapping is restored from the local cache.

2.11.2 SOZCM0002

Failed to restore file mappings

Explanation:

The file mappings could not be restored from the cached data in the Eclipse workspace.

User response:

Verify that the file file_mapping.xml file exists in the internal project folder in the user's workspace

and is accessible.

Verify that the file_mapping.xml file is a valid XML file. If not, try to repair it. If not possible remove

the file from the internal project folder and build up the file mappings from scratch.

2.11.3 SOZCM0003

The number of the given values does not match the number of the given attributes.

Explanation:

This is an internal program exception. An API method was called which generates XML attributes

from passed keywords and values but the number of keywords and values was not equal.


If the call was made from a custom plug-in correct the passed parameters. Otherwise contact

customer support.

2.11.4 SOZCM0004

Password is invalid.

Explanation:

An invalid host password was specified.

User response:

Use the correct password.


Page: 145

2.11.5 SOZCM0005

The entered password is too long.

Explanation:

The password entered by the user is too long.

User response:


2.11.6 SOZCM0006

The password is too long. Max. length is 8 characters.

Explanation:

The password entered by the user is too long.

User response:


2.11.7 SOZCM0007

Error from z/Server ADDUSRV command: {0}

Explanation:

The ADDUSRV command to start another z/Server user server failed.



2.11.8 SOZCM0008

Action cancelled by user.

Explanation:

self-explanatory

User response:



Page: 146

2.11.9 SOZCM0009

Data set allocation error: {0}

Explanation:

An error occurred during the allocation of a z/OS data set.

User response:





2.11.10 SOZCM0010

{0} is not a full qualified member name (DSN member name)

Explanation:

The data set name passed to the routine to browse a load module has not the expected format.



2.11.11 SOZCM0011

Failed to get contents for data set {0}

Explanation:

The content of the given z/OS data set could not be read.





2.11.12 SOZCM0012

pMsg must not be null.

Explanation:

The message parameter passed to the routine which sends messages to the server is null which is


Page: 147

not valid.



2.11.13 SOZCM0013

User not defined to RACF

Explanation:

The user ID specified is not defined to RACF on the remote z/OS system.

User response:

Verify that the user specified the correct user ID.

2.11.14 SOZCM0014

Password not authorized

Explanation:

The given password is incorrect.

User response:

Retry with the correct password.

2.11.15 SOZCM0015

The password has expired

Explanation:

The given password has expired.

User response:

Use the change password dialog to get a new password.

The change password dialog must be called while not disconnected to z/Server.

2.11.16 SOZCM0016

The new password is invalid

Explanation:


Page: 148

The new password specified in the Change Password dialog is not valid.

User response:

Enter a valid password in the Change Password dialog.

2.11.17 SOZCM0017

User not defined to group

Explanation:

The user is not defined to a RACF group.

User response:

Contact the z/OS RACF administrator.

2.11.18 SOZCM0018

User access revoked

Explanation:

The user ID is revoked in RACF.

User response:


2.11.19 SOZCM0019

RACF is not active

Explanation:

The z/OS RACF facility is not active.

User response:


2.11.20 SOZCM0020

User access to group revoked

Explanation:


Page: 149

The access of the user to the requested RACF group is revoked.

User response:


2.11.21 SOZCM0021

OID REQD not supplied

Explanation:

The RACF OID REQD was not supplied.



2.11.22 SOZCM0022

OID CARD invalid for user

Explanation:

The RACF OID CARD was not valid for the user.

User response:


2.11.23 SOZCM0023

User not authorized to terminal

Explanation:

The user is not authorized by RACF to use a terminal by RACF.

User response:


2.11.24 SOZCM0024

User not authorized to APPL

Explanation:


Page: 150

The user is not authorized in RACF class APPL.

User response:


2.11.25 SOZCM0025

RACF verify for user ID not successful

Explanation:

The given user ID did not pass the RACF user ID validation.

User response:

Retry with the correct password.


2.11.26 SOZCM0026

Access to data set {0} denied

Explanation:

The user does not have access to the given data set.

User response:


2.11.27 SOZCM0027

Unexpected length field: {0}

Explanation:

There was a non-numeric field detected reading a file that is encrypted using BASE64. A numeric

length field was expected.







Page: 151

2.11.28 SOZCM0028

Parsing of GETDATA response failed. Warning Message(s) from server: {0}

Explanation:

An error occurred when the response from the remote system was parsed.

User response:

Check the subsequent message from the z/Server.




2.11.29 SOZCM0029

The GETDATA response from server could not be parsed.

Explanation:

The response from z/Server to a GETDATA request has an invalid format.



2.12 z/Server ISPF Panel Support (TSIPS)

2.12.1 TSIPS0001

Failed to parse help panel {0}

Explanation:

The help panel associated with an ISPF panel could not be located in the given input partitioned data

set. This means the help panel could not be parsed and the help information could not be registered

to the corresponding attribute of the ISPF dialog tool.

User response:

If help information should be added to the model, add the missing help panel to the data set specified

in the corresponding location attribute in the panel generation control file.

Then repeat the model generation.

2.12.2 TSIPS0002

Given options map must not be null.


Page: 152

Explanation:

An internal object was null where it was not expected to be null.



2.12.3 TSIPS0003

XML syntax error: A {0} element contains at least one {1} element. No {2} attribute is set.

Explanation:

There is an error in the XML structure of the panel model generator control file.

A line command is defined for a panel although there is no table defined for the panel.

User response:

Correct the error in the panel model generator control file.

If there are line commands defined for a panel, a table attribute must be specified in the XML panel

tag.

Remove the line commands or add the table attribute.

2.12.4 TSIPS0004

There is no {0} included in {1} element.

Explanation:

In the panel model generator control file an application is defined with no associated panels.

User response:

This is a warning message. Verify that the XML definition was intended in this way.

2.12.5 TSIPS0005

A {0} element contains more than one {1} element with the {2} attribute: {3}

Explanation:

The same panel was declared more than once for the same application in the panel model generator

control file.

User response:

This is warning message. Only one ISPF dialog tool will be generated if the same panel is declared


Page: 153

more than once for the same application.

2.12.6 TSIPS0006

XML syntax error: At least one {0} attribute must be specified for {1} attribute ComboBox.

Explanation:

A selection field was defined, but no selection values were given for a panel field in the panel model

generator control file.

User response:

Correct the panel model generator control file by listing the selection values.

2.12.7 TSIPS0007

XML syntax error: No {0} is set.

Explanation:

The location attribute for a panel entry in the panel model generator control file could not be found.

User response:

Correct the panel model generator control file by defining the location in the overallAttr, dialogAppl

or panel XML tag.

2.12.8 TSIPS0008

Panel extension error: parameter string for panel REXX in panel {0} call too long. Not all panel

variables are passed to the panel REXX!

Explanation:

There is a technical restriction that the length of the field names passed to a ISPF Panel REXX must

not exceed 255 characters in total.

The conversion of the given panel caused a field name length greater than 255. This means that

during the execution of the ISPF dialog in an Eclipse environment not all of the variables' contents

are passed to the client which will cause unpredictable results.

User response:

Try to change the ISPF panel so that less panel fields must be passed to the Eclipse dialog.

2.12.9 TSIPS0009

An error has occurred. See error log for more details.


Page: 154

Explanation:

The XML SAX parser detected an error.

User response:

There is a log file of the panel conversion in the FileCache sub folder of the internal project folder.

See this log file for more information about the XML error.

2.12.10 TSIPS0010

Command Property is not defined in relation ISA_ISPF_Panel_Command for {0}

Explanation:

The command property is missing in the ISA_ISPF_Panel_Command relation for the given tool in

the model.


Correct the error in the ISA_ISPF_Panel_Command relation of the given tool in the XML model file.

Select the command property.

2.12.11 TSIPS0011

Relation ISA_ISPF_Panel_Command is missing for {0}

Explanation:

The relation ISA_ISPF_Panel_Command for the given tool is missing.

This relation is needed if a tool is defined as part of a line command action for a file descriptor.


Add an ISA_ISPF_Panel_Command relation to the given tool in the XML model file.

2.12.12 TSIPS0012

Exception occurred during ISPF dialog processing.

Explanation:

An exception occurred during the execution of an ISPF dialog tool.




Page: 155



2.12.13 TSIPS0015

Exception when connecting to system {0} .

Explanation:

The connection to the given remote system could not be established.

User response:

Verify that there is a network connection problem to the remote system.

Verify that the connection attributes of the remote system (IP address and port) are set correctly.

2.12.14 TSIPS0016

IO exception when trying to read host message

Explanation:

An I/O exception on the network socket occurred during the execution of an ISPF dialog

application.

User response:

Disconnect and re-connect to the remote system.





Verify that there is no network problem between client and server.


2.12.15 TSIPS0017

IO Exception when sending a message to the user server

Explanation:

An I/O exception on the network socket occurred during the execution of an ISPF dialog


Page: 156

application.

User response:

Disconnect and re-connect to the remote system.







2.12.16 TSIPS0018

Your dialog has timed out. Please restart the dialog.

Explanation:

The given dialog was open for a time interval longer than the configured time out period without any

user interaction.

User response:


Restart the ISPF dialog application.

2.12.17 TSIPS0019

z/Server Exception during to connection to port: {0}

Explanation:

An exception occurred during the communication of an ISPF dialog application and its associated

user server.






2.12.18 TSIPS0020

No ISPF help available for {0} .


Page: 157

Explanation:

There is no help panel defined for the given ISPF dialog tool.

User response:


2.12.19 TSIPS0021

User socket is null.

Explanation:

The network socket for the communication with the remote system has become undefined.





Page: 158

3 Troubleshooting

The first step to troubleshooting is to determine the Application Workflow Manager component the

problem occurred in.

There is a general differentiation between two components:

z/Explorer

Modelled Application Workflow Manager application

The type of an Application Workflow Manager component and where the error occurred determine

the analysis methods required.

Some error situations are caused by a temporary failure; for example, the IP communication socket

between the client and the z/Server might not be ready for communication.

In such cases, you will typically receive an org.xml.sax.SAXParseException message, sometimes with

the reason “Content not allowed in prolog.”. Communication between the client and z/Server scheduler

address space is in XML format. When the client does not receive an expected XML response (for

instance because the scheduler address space is temporarily unavailable), a SAX exception occurs. In

this case, first try to repeat the same action, it might work. The next chapter describes general

troubleshooting methods which apply to all components. Special methods for z/Explorer and

modelled Application Workflow Manager applications are described in separate chapters.

3.1 General Problem Determination

In order to determine the cause of a problem as much information as possible needs to be gathered.

Try to answer as many of the following questions as possible:

Which version of the Application Workflow Manager software is installed on your system?

What error message, if any, is displayed? What additional information is displayed when you

click Details>>.

Are there any entries in the error log relating to this error situation?

What did you do, how did you expect the system to react and how did the system really

react?

Is the problem reproducible?

Does the problem only occur under certain conditions (e.g. only with certain input data or on

certain types of element)? If so, what are they?

Does the problem only occur in your environment or is it a general problem for all users?

Does the problem persist after restarting your Eclipse workbench?

If the problem is to be reported to the Micro Focus SupportLine, a number of things are required to

be collected:

Detailed problem description

Screenshots of error messages

Screenshots of unexpected behavior

Error logs


Page: 159

Refer to 3.4General Problem Solving Suggestions

This chapter lists some general methods and technics which can be helpful for troubleshooting.

3.1.1 Determine the original exception

In some cases the error message dialog will display more than one error message. The reason for it

is that special exceptions are wrapped by less specific exceptions before they are issued.

In order to find the basic cause of the error situation, the original exception has to be determined.

Typically this is the last exception of the list of exceptions in the details window.

3.1.2 Clear The Persistent Cache In The Workspace

The information displayed in the Application Workflow Manager view is persistently stored in the

Eclipse workspace in several XML files when the Eclipse workbench is shut down or an application is

unloaded. See the Workflow Manager Configuration Guide for more information about those cache

files.

In some error situations it might be necessary to clear the cache, for example if the cache has got

inconsistent with the model or if there are error messages indicating an inconsistent cache. It is

strongly recommended to use for this purpose the “Clear Cache…” action in the context menu of

an application in the Tree View:

In this way it is ensured that the cache is cleared in a consistent way.

In some special situation it might be necessary to delete the files directly in the file system. This

should only be done in accordance or by order of the customer support. In this case it is important

that Eclipse is shut down before the files are deleted.


Page: 160

3.1.3 Deal With Code Page Problems

If problems occur which indicate a code page problem although the code page is set correctly in the

zServer properties of the MVS Explorer in the Remote System View, always verify if there is a

special file mapping for the regarding file. If this is the case, verify the code page setting in this file

mapping.

3.1.4 Workspace Out Of Sync

The Eclipse workspace where the Application Workflow Manager files are lying can get out of

synchronisation with underlying file system. This can be corrected by applying the refresh action in

the Navigator view to the part of the Application Workflow Manager project which has got out of

synchronisation.

Gathering Information for the Micro Focus SupportLine for details on how to assemble the

information required by Micro Focus SupportLine.

3.2 z/Explorer Problem Determination

When an error occurs in z/Explorer, typically an error message is displayed. If the error contains a

message ID in the format described in chapter 1, refer to z/Server Messages for more information

about the cause and possible responses.

If the error displayed is a software exception message, refer to the error log view for more

information.

If none of the above helps in solving the problem, send the error log to Micro Focus; refer to

chapter 3.4General Problem Solving Suggestions











files.


Page: 161













mapping.





synchronisation.

Gathering Information for the Micro Focus SupportLine.


Page: 162

3.3 Application Workflow Manager Problem Determination

The functionality of an application in the Team Developer Tree View is based on an XML model file.

In most cases, a problem in a modelled application can be traced back to an error or inconsistency

in the application model. As a general rule, the Application Workflow Manager model administrator

should validate a model file before it is set productive. Validate a model file by clicking , which is

displayed on the Eclipse toolbar when editing a model file. Errors reported by the validation should

always be corrected before the model file is set productive.

If problems in a modelled application are reported to the Micro Focus SupportLine, it is important

to include the application model file. To do this, open Navigator View from the Eclipse workbench.

In Navigator View, expand the InternalTDProject entry to the level of the application that is

currently active in the Team Developer Tree View. The corresponding model file TAURCONF.xml

for the active application is displayed.

Include a copy of this file in the information to be sent to Micro Focus SupportLine.

The next five sub-chapters require some knowledge of Application Workflow Manager application

modelling. They are meant as help for the Application Workflow Manager model administrator to

correct some typical error situations caused by an inconsistent application model.


Page: 163

3.3.1 Modelled Action Does Not Work

Check the reference to the Action Descriptor (e.g. “Element has Action”):

Is there a reference to an Action Descriptor in the respective Element Type?

Is the correct Action Descriptor referenced?

Check the Action Descriptor:

Are the references to the Tool Descriptors correct (including sequence numbers)?

Check the Tool Executor(s):

Are the parameters correctly modelled?

Does the Type attribute match the Target ID used? In most cases parameters

that reference a file descriptor (TargetID File) must be modelled with the

attribute Type = File while parameters pointing at a property (TargetID Parm)

must have the attribute Type = String

Is the Parameter From attribute of all input parameters correct?

Context – The value will be taken from context (properties of the selected

Element).

Previous Tool – The value will be taken from previous tool of the corresponding

Action Descriptor.

User Input – No value is used (only for Input Dialogs).

Remember that you can also use a Default or Static Value

If Tool Type = ISPFCOMMAND

Is the “ISA ISPFTool” attribute modelled?

Is the Program ID spelled correctly?

Is the correct Invocation Form specified?

Are parameter separators modelled correctly?

3.3.2 Element List is Not Created

If a detailed error dialog is displayed (containing the parsed line for element list creation):

Use the “Validate” action of the Application Workflow Modeller. If errors were

detected, try to correct them.

In the error dialog:

Were the values of the parsed line parsed properly?

Is the match name (Element Type name) on the parsed line?

Is the match name’s position correct (depending on the position of the Element

Type Property)?

Does the parsed line contain every Property of the Element Types ID Definition?


Page: 164

If no detailed error dialog is displayed:

If the element list should be shown in Table View (no Get Children action):

Is an Element List Structure modelled for the corresponding Action Descriptor

(attribute Has Elementlist)?

3.3.3 Tree View is Not Expandable

If the Tree View Element is the Application itself:

Was an Action Descriptor defined in the Get Root Containers attribute of the

Application Options?

If the Tree View Element is an Element of a modelled Element Type:

Was an Action Descriptor defined in the Get Children attribute of the corresponding

Element Type?

“Refresh” the Tree View Element that is not expanding:

Explanation: The Application Workflow Manager caches Tree View information. If the

expand fails because of an incorrect model an empty list is cached.

3.3.4 Tree View Elements Do Not Have a Correct Label

Check the Tree View Label attributes of the corresponding Element Type. The attribute can

be found in the “Element Type has Property” relationship.

3.3.5 Edit Action (Simple Remote Edit or Browse) Does Not Work Properly

If the editor does not open, check the Tool Descriptor that should open it:

The attribute Integrated Tool must be set to RemoteEdit.

An input parameter must be configured:

Type = File

TargetID File = Unstructured Tool Descriptor. Check that the Name Physical

attribute references the correct Property IDs.

If the editor opens, but the editor title/label is “null”:

Check that exactly one Property of the corresponding Element Type has the Element

Name attribute set to true. The attribute is in the “Element Type has Property”

relationship.

The editor opens with the wrong suffix (.txt):

Does the corresponding Element Type have a relationship to a suffix Property?


Page: 165

Does the suffix Property have the attribute Special Property = Element_Suffix?

The wrong editor opens up:

In Eclipse, click Window > Preferences > General > Editors > File Associations

and configure which editor should open up for the file extension (suffix).

3.4 General Problem Solving Suggestions











files.






Page: 166









mapping.





synchronisation.

3.5 Gathering Information for the Micro Focus SupportLine

When a user problem cannot be resolved by the Application Workflow Manager model

administrator/system administrator, report the problem to the Micro Focus SupportLine.


Page: 167

Include debug information from the error logs to help further analysis of a problem. To include this

information, create an .options file and save it in the installation path of the Enterprise Developer

product.


Page: 168

The .options file must contain the following:

de.soforte.taurus/debug=true

de.soforte.taurus/debug/flag=true

de.soforte.taurus.mvssystem/debug=true

de.soforte.taurus.mvssystem/debug/flag=true

de.soforte.zserver.communicator/tracing=true

You can edit this file with Notepad or any similar text editor.

To quickly find the installation path when saving the .options file click Open File Location from

the Enterprise Developer shortcut.

After the .options file has been created and saved to the installation path, restart the Eclipse

workbench with the –debug option (append ‘-debug’ to the Target field shown above).

Reproduce the error and export the error log to a local file (click Error Log View from the

Eclipse workbench).


Page: 169

Add the exported file to all other information (problem description, screenshots, etc.) for

SupportLine and zip it up ready to attach to an incident raised with the Micro Focus SupportLine.

Remove the –debug option from the Target field.

You can also add debug information to a remote z/Server user server address space by activating the

REXX debug as described in the Workflow Manager Configuration Guide.


Page: 170

4 Sample Error Situations

4.1 z/Server Is Not Active

If z/Server is not active on the remote system, an error message similar to the one below is

displayed when connecting to z/Server:

4.2 Connection To z/Server Is Interrupted

If the network connection between client and remote system is interrupted an error message similar

to the one below is displayed when connecting to z/Server:

When z/Server is not active, the same message is received. The same error message can have

different reasons.


Page: 171

4.3 Connection Problem When Connection Is Active

When network connection problems occur while already connected to a remote system (z/Server),

an error message similar to the one below is displayed:

The connection problem occurred while closing a file in the editor. The action "delete the local copy

of the file" could not be executed. The reason is a time-out because of connection problems.

4.4 No RACF OMVS Segment

If there is no RACF OMVS segment defined to the TSO user ID used to execute an ISPF tool using

an Application Workflow Manager modelled application, the following error message is displayed:


Page: 172

This message was issued by z/Server (the remote software), the scheduler address space in

particular. The scheduler address space had started the user server address space needed to

establish the master configuration data set that contains the ISPF application. That address space did

come up, but was unable to signal itself READY to the scheduler address space. Message SLR0131E

is issued to the client after a predefined wait period to tell the client that it could not talk to the

user server address space.

The administrator for z/Server needs to check for errors. For this particular problem, the z/OS

hardcopy log shows:

ICH408I USER(user ) GROUP(group ) NAME(####################)

CL(PROCESS )

OMVS SEGMENT NOT DEFINED

Job output in user server maintask has this error message again detailing the missing OMVS RACF

segment:

TAU0143S 07:35:19.091 This indicates an z/OS UNIX process initialisation

failure.

This is usually an indication that a proper OMVS

RACF segment

is not defined for the user ID associated with the

application

The RACF OMVS segment may not be defined or may

contain error

such as an improper HOME() directory

specification.

TAU0139E 07:35:24.094 SVC with function code 00000800 failed with RC

00000008

In this case, the TSO user ID must be defined with an OMVS segment (usually done by the RACF

administrator) as detailed in the z/Server Installation and Reference.

4.5 Model Error: Wrong Program ID

If the Application Workflow Manager model administrator defined a wrong Program ID in the ISA

ISPF Tool relation of a tool descriptor, the following error message is displayed:


Page: 173

4.6 Model Error: Wrong Panel Name

If the Application Workflow Manager model administrator defined a wrong Panel Name in the ISA

ISPF Panel relation of a tool descriptor for an ISPF dialog tool, the following error message is

displayed:

4.7 Error Situations in an Attached Tool

If one of the pre-configured Application Workflow Manager models (PDS Explorer, SCLM

Application, ChangeMan Application) or custom application models based on the REXX tool adapter

TAUTOSAM are used, the attached tools will report error situations in a defined way.

For a deeper understanding of the methods and techniques of Application Workflow Manager tool

attachment, please see the Workflow Manager Configuration Guide.

Application Workflow Manager displays an error message when the return code of the attached tool

is higher than the value specified by the Application Workflow Manager model administrator under

the property Max RC of Application Options in the Application Workflow Manager model. The

recommended value for Max RC is 4. Then the following error message is displayed:

Within the message, return code and message returned by the attached tool are shown.

The following table shows special return codes generally used in pre-configured Application

Workflow Manager models, specifically in models based on the REXX tool adapter TAUTOSAM.

Return code Meaning


Page: 174

0 Attached tool successfully executed; no message window is displayed

11 The return code of the facility called (such as TSO or ISPF) is higher than the

maximum return code specified in the facility call. The message contains the

command called and the return code produced by the facility. Look up the meaning

of the return code in the corresponding IBM book under the command reported

by the message.

99 Undefined variable referenced or syntax error in the attached tool

In addition to these special return codes, attached tools can return custom created return codes and

messages. If the REXX TAUTOSAM is used as a template for custom tool adapters, these custom

messages are reported with the same formatting.

The following examples shows the error messages displayed when certain error situations occur

within an attached tool.

Undefined variable used in the attached tool:

Syntax error in the attached tool:


Page: 175

Call to ISPF command VGET returns a return code higher than the maximum return code

allowed ( 4):

Looking in REXX TAUPDGJK the error was produced by a call to ISPF command VGET:

Call ISPF '0 VGET (ZUSERA) SHARED'

IBM ISPF Services Guide for command VGET shows the following under return code 8:

Variable not found. If the SYMDEF parameter was specified: system symbol

not found.

Custom return code:

The custom tool TOOL_Getdatasets returned with a return code of 12, which is higher than Max

RC of 4 specified under Application Options in the Application Workflow Manager model. The

message returned by the tool is “This is a customer specific error situation…”.


Page: 176

5 Known Issues

In this chapter known issues and possible work-arounds are provided.

The port of a z/Server connection is not remembered

Description:

When a new z/Server connection is created and the Eclipse workbench is exited without connecting

to this new connection, the port is set back to the default value 1111 when the Eclipse workbench is

re-entered.

Auxiliary solution:

You should always connect to a newly created z/Server connection before exiting the Eclipse

workbench.

Change password when connected

Description:

If the Change Password… action is used on a z/Server connection that is actively connected to a

remote host, this can lead to subsequent problems.

Auxiliary solution:

Use the Change Password… action only on a z/Server connection that is not connected.

Change code page settings when connected

Description:

If the code page settings of the MVS Explorer are changed on a z/Server connection that is actively

connected to a remote host, certain action won’t work correctly afterwards.

Auxiliary solution:

Change the code page settings only on a z/Server connection that is not connected.


Page: 177

Multi-selection in ISPF table dialogs with non-keyed tables

Description:

In modelled ISPF table dialogs with non-keyed tables multi-selection of table entries doesn’t work

correctly.

Auxiliary help:

ISPF table dialogs of non-keyed ISPF tables with multi-selection line commands cannot yet be

modelled.


Page: 178

6 Bibliography

z/Server Installation Guide and Reference

z/Server Messages

Workflow Manager Configuration Guide

Workflow Manager Messages and Troubleshooting - Micro Focus · 2014-05-15 · Workflow Manager...

Documents

Transcript of Workflow Manager Messages and Troubleshooting - Micro Focus · 2014-05-15 · Workflow Manager...