Change data transfer

For change data transfer,i started a journal first ,a session got started . I then inserted a row into the source table,when i executed the model,there was no error and it got executed.But when i viewed the jounal data in the model.....the changes did not get reflected in journal data. What steps do i follow to capture the chaged data.( both added adn deleted).

Hi,
I really do not think you need to worry about Agent. I have done this many times without any agents.
In the steps I gave, I forgot to add one step. Please disregard if you have already done this.
Right click on the datastore and go to Change data capture and say Add to CDC. WHen you do this you see a clock symbol on the data store.
Now, follow the steps to register subscriber and Start journal. When you see in the OPerator that the session is successful, go to the Designer and refresh Model or Datastore. You will see a green clock symbol which means that the Journal is started. Now, you go and make changes on the datastore you should be able to see the changes in J$ and JV$D.
Regards,
kk

Similar Messages

Change data transfer rate ?

Hi there,
I have installed a new WD 1tb internal hard drive in my late 2006 iMac . I've managed to get over a problem I posted about earlier namely getting the Snow Leopard disc out and using my original Tiger 10.4 discs. Trouble now is despite following the instructions for formatting my new hard drive I keep getting input\output error coming up . I've googled a lot and I believe it may be because my intel Mac supports 1.5gbs a second transfer rate whilst the hard drive is 6gbs . I have a caviar blue advanced drive that has no jumpers to change , but I'm led to believe that would be the answer . I'm relatively new to all this but are there jumpers in the mac itself ? Or is there a way to change the rate so my Mac accepts and formats the drive ? On various sites it says the drive is compatible but not how to do this. Hope it makes sense lads I'm sooo stressed .
Cheers

Transfer rate won't cause this problem. Your Mac will only transfer data as fast/slow as it can, 1.5gbs. The HD transfer rate will automatically slow to 1.5gbs.
What did you use to format the HD and what format did you use? It should be formatted to 'Mac OS Extended (Journaled)'. This can be easily done using the Disk Utility app that comes with OSX.
Usually the jumpers are for making the HD a master or slave drive. You shouldn't have to mess with the new HD settings to make it work.

Approaches to transfer changed data from a table to another table

Hello expert,
will you please show me all approaches to automatically detect and transfer changed data from a table to another table ? I don't need detail information, but a little comment for those approaches are more welcome.
Many Thanks,
Edited by: 843178 on 19-Dec-2011 2:04 PM

You will want to review information on replication and similar methods
In a nutshell:
Replication allowed data to exist at more than one site and take the Master / original table data and clone it at a different site
As tranporting all of the table data to a remote / clone site got more and more expensive we developed a method
to identify just the 'diffs' and only send those from the master to the clone which needed only the diffs to become a clone of the master table
This has many methods and options, but looking under key words such as
- distributed transations
- materialized views
- replication
... are a few categories that will get you started

How to find the max data transfer rate(disk speed) supported by mobo?

I plan on replacing my current HDD with a new and bigger HDD.
For this I need to know the max data transfer rate(disk speed) that my mobo will support. However, dmidecode is not telling me that. Am I missing something?
Here's dmidecode:
# dmidecode 2.11
SMBIOS 2.5 present.
80 structures occupying 2858 bytes.
Table at 0x000F0450.
Handle 0xDA00, DMI type 218, 101 bytes
OEM-specific Type
Header and Data:
DA 65 00 DA B2 00 17 4B 0E 38 00 00 80 00 80 01
00 02 80 02 80 01 00 00 A0 00 A0 01 00 58 00 58
00 01 00 59 00 59 00 01 00 75 01 75 01 01 00 76
01 76 01 01 00 05 80 05 80 01 00 D1 01 19 00 01
00 15 02 19 00 02 00 1B 00 19 00 03 00 19 00 19
00 00 00 4A 02 4A 02 01 00 0C 80 0C 80 01 00 FF
FF 00 00 00 00
Handle 0xDA01, DMI type 218, 35 bytes
OEM-specific Type
Header and Data:
DA 23 01 DA B2 00 17 4B 0E 38 00 10 F5 10 F5 00
00 11 F5 11 F5 00 00 12 F5 12 F5 00 00 FF FF 00
00 00 00
Handle 0x0000, DMI type 0, 24 bytes
BIOS Information
Vendor: Dell Inc.
Version: A17
Release Date: 04/06/2010
Address: 0xF0000
Runtime Size: 64 kB
ROM Size: 4096 kB
Characteristics:
PCI is supported
PNP is supported
APM is supported
BIOS is upgradeable
BIOS shadowing is allowed
ESCD support is available
Boot from CD is supported
Selectable boot is supported
EDD is supported
Japanese floppy for Toshiba 1.2 MB is supported (int 13h)
3.5"/720 kB floppy services are supported (int 13h)
Print screen service is supported (int 5h)
8042 keyboard services are supported (int 9h)
Serial services are supported (int 14h)
Printer services are supported (int 17h)
ACPI is supported
USB legacy is supported
BIOS boot specification is supported
Function key-initiated network boot is supported
Targeted content distribution is supported
BIOS Revision: 17.0
Handle 0x0100, DMI type 1, 27 bytes
System Information
Manufacturer: Dell Inc.
Product Name: OptiPlex 755
Version: Not Specified
UUID: 44454C4C-5900-1050-8033-C4C04F434731
Wake-up Type: Power Switch
SKU Number: Not Specified
Family: Not Specified
Handle 0x0200, DMI type 2, 8 bytes
Base Board Information
Manufacturer: Dell Inc.
Product Name: 0PU052
Version:
Handle 0x0300, DMI type 3, 13 bytes
Chassis Information
Manufacturer: Dell Inc.
Type: Space-saving
Lock: Not Present
Version: Not Specified
Asset Tag:
Boot-up State: Safe
Power Supply State: Safe
Thermal State: Safe
Security Status: None
Handle 0x0400, DMI type 4, 40 bytes
Processor Information
Socket Designation: CPU
Type: Central Processor
Family: Xeon
Manufacturer: Intel
ID: 76 06 01 00 FF FB EB BF
Signature: Type 0, Family 6, Model 23, Stepping 6
Flags:
FPU (Floating-point unit on-chip)
VME (Virtual mode extension)
DE (Debugging extension)
PSE (Page size extension)
TSC (Time stamp counter)
MSR (Model specific registers)
PAE (Physical address extension)
MCE (Machine check exception)
CX8 (CMPXCHG8 instruction supported)
APIC (On-chip APIC hardware supported)
SEP (Fast system call)
MTRR (Memory type range registers)
PGE (Page global enable)
MCA (Machine check architecture)
CMOV (Conditional move instruction supported)
PAT (Page attribute table)
PSE-36 (36-bit page size extension)
CLFSH (CLFLUSH instruction supported)
DS (Debug store)
ACPI (ACPI supported)
MMX (MMX technology supported)
FXSR (FXSAVE and FXSTOR instructions supported)
SSE (Streaming SIMD extensions)
SSE2 (Streaming SIMD extensions 2)
SS (Self-snoop)
HTT (Multi-threading)
TM (Thermal monitor supported)
PBE (Pending break enabled)
Version: Not Specified
Voltage: 0.0 V
External Clock: 1333 MHz
Max Speed: 5200 MHz
Current Speed: 2666 MHz
Status: Populated, Enabled
Upgrade: Socket LGA775
L1 Cache Handle: 0x0700
L2 Cache Handle: 0x0701
L3 Cache Handle: Not Provided
Serial Number: Not Specified
Asset Tag: Not Specified
Part Number: Not Specified
Core Count: 2
Core Enabled: 2
Thread Count: 2
Characteristics:
64-bit capable
Handle 0x0700, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 1
Operational Mode: Write Back
Location: Internal
Installed Size: 32 kB
Maximum Size: 32 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: None
System Type: Data
Associativity: 8-way Set-associative
Handle 0x0701, DMI type 7, 19 bytes
Cache Information
Socket Designation: Not Specified
Configuration: Enabled, Not Socketed, Level 2
Operational Mode: Varies With Memory Address
Location: Internal
Installed Size: 6144 kB
Maximum Size: 6144 kB
Supported SRAM Types:
Other
Installed SRAM Type: Other
Speed: Unknown
Error Correction Type: Single-bit ECC
System Type: Unified
Associativity: <OUT OF SPEC>
Handle 0x0800, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: PARALLEL
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-25 female
Port Type: Parallel Port PS/2
Handle 0x0801, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: SERIAL1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-9 male
Port Type: Serial Port 16550A Compatible
Handle 0x0802, DMI type 126, 9 bytes
Inactive
Handle 0x0803, DMI type 126, 9 bytes
Inactive
Handle 0x0804, DMI type 126, 9 bytes
Inactive
Handle 0x0805, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB1
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0806, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB2
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0807, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB3
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0808, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB4
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x0809, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB5
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080A, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB6
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080B, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB7
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080C, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: USB8
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Access Bus (USB)
Port Type: USB
Handle 0x080D, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: ENET
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: RJ-45
Port Type: Network Port
Handle 0x080E, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MIC
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x080F, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0810, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: LINE-IN
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0811, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: HP-OUT
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: Mini Jack (headphones)
Port Type: Audio Port
Handle 0x0812, DMI type 8, 9 bytes
Port Connector Information
Internal Reference Designator: MONITOR
Internal Connector Type: None
External Reference Designator: Not Specified
External Connector Type: DB-15 female
Port Type: Video Port
Handle 0x090A, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT1
Type: x1 Proprietary
Current Usage: In Use
Length: Long
Characteristics:
PME signal is supported
Handle 0x0901, DMI type 126, 13 bytes
Inactive
Handle 0x0902, DMI type 9, 13 bytes
System Slot Information
Designation: SLOT2
Type: 32-bit PCI
Current Usage: Available
Length: Long
ID: 2
Characteristics:
5.0 V is provided
3.3 V is provided
PME signal is supported
Handle 0x0903, DMI type 126, 13 bytes
Inactive
Handle 0x0904, DMI type 126, 13 bytes
Inactive
Handle 0x0905, DMI type 126, 13 bytes
Inactive
Handle 0x0906, DMI type 126, 13 bytes
Inactive
Handle 0x0907, DMI type 126, 13 bytes
Inactive
Handle 0x0908, DMI type 126, 13 bytes
Inactive
Handle 0x0A00, DMI type 10, 6 bytes
On Board Device Information
Type: Video
Status: Disabled
Description: Intel Graphics Media Accelerator 950
Handle 0x0A02, DMI type 10, 6 bytes
On Board Device Information
Type: Ethernet
Status: Enabled
Description: Intel Gigabit Ethernet Controller
Handle 0x0A03, DMI type 10, 6 bytes
On Board Device Information
Type: Sound
Status: Enabled
Description: Intel(R) High Definition Audio Controller
Handle 0x0B00, DMI type 11, 5 bytes
OEM Strings
String 1: www.dell.com
Handle 0x0D00, DMI type 13, 22 bytes
BIOS Language Information
Language Description Format: Long
Installable Languages: 1
en|US|iso8859-1
Currently Installed Language: en|US|iso8859-1
Handle 0x0F00, DMI type 15, 29 bytes
System Event Log
Area Length: 2049 bytes
Header Start Offset: 0x0000
Header Length: 16 bytes
Data Start Offset: 0x0010
Access Method: Memory-mapped physical 32-bit address
Access Address: 0xFFF01000
Status: Valid, Not Full
Change Token: 0x00000018
Header Format: Type 1
Supported Log Type Descriptors: 3
Descriptor 1: POST error
Data Format 1: POST results bitmap
Descriptor 2: System limit exceeded
Data Format 2: System management
Descriptor 3: Log area reset/cleared
Data Format 3: None
Handle 0x1000, DMI type 16, 15 bytes
Physical Memory Array
Location: System Board Or Motherboard
Use: System Memory
Error Correction Type: None
Maximum Capacity: 8 GB
Error Information Handle: Not Provided
Number Of Devices: 4
Handle 0x1100, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_1
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Manufacturer: AD00000000000000
Handle 0x1101, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_3
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1102, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_2
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1103, DMI type 17, 27 bytes
Memory Device
Array Handle: 0x1000
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 1024 MB
Form Factor: DIMM
Set: None
Locator: DIMM_4
Bank Locator: Not Specified
Type: DDR2
Type Detail: Synchronous
Speed: 667 MHz
Handle 0x1300, DMI type 19, 15 bytes
Memory Array Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x000FDFFFFFF
Range Size: 4064 MB
Physical Array Handle: 0x1000
Partition Width: 1
Handle 0x1400, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1100
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1401, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1101
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 1
Interleaved Data Depth: 1
Handle 0x1402, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00000000000
Ending Address: 0x0007FFFFFFF
Range Size: 2 GB
Physical Device Handle: 0x1102
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1403, DMI type 20, 19 bytes
Memory Device Mapped Address
Starting Address: 0x00080000000
Ending Address: 0x000FDFFFFFF
Range Size: 2016 MB
Physical Device Handle: 0x1103
Memory Array Mapped Address Handle: 0x1300
Partition Row Position: 1
Interleave Position: 2
Interleaved Data Depth: 1
Handle 0x1410, DMI type 126, 19 bytes
Inactive
Handle 0x1800, DMI type 24, 5 bytes
Hardware Security
Power-On Password Status: Enabled
Keyboard Password Status: Not Implemented
Administrator Password Status: Enabled
Front Panel Reset Status: Not Implemented
Handle 0x1900, DMI type 25, 9 bytes
System Power Controls
Next Scheduled Power-on: *-* 00:00:00
Handle 0x1B10, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD00
Handle 0x1B11, DMI type 27, 12 bytes
Cooling Device
Type: Fan
Status: OK
OEM-specific Information: 0x0000DD01
Handle 0x1B12, DMI type 126, 12 bytes
Inactive
Handle 0x1B13, DMI type 126, 12 bytes
Inactive
Handle 0x1B14, DMI type 126, 12 bytes
Inactive
Handle 0x2000, DMI type 32, 11 bytes
System Boot Information
Status: No errors detected
Handle 0x8100, DMI type 129, 8 bytes
OEM-specific Type
Header and Data:
81 08 00 81 01 01 02 01
Strings:
Intel_ASF
Intel_ASF_001
Handle 0x8200, DMI type 130, 20 bytes
OEM-specific Type
Header and Data:
82 14 00 82 24 41 4D 54 01 01 00 00 01 A5 0B 02
00 00 00 00
Handle 0x8300, DMI type 131, 64 bytes
OEM-specific Type
Header and Data:
83 40 00 83 14 00 00 00 00 00 C0 29 05 00 00 00
F8 00 4E 24 00 00 00 00 0D 00 00 00 02 00 03 00
19 04 14 00 01 00 01 02 C8 00 BD 10 00 00 00 00
00 00 00 00 FF 00 00 00 00 00 00 00 00 00 00 00
Handle 0x8800, DMI type 136, 6 bytes
OEM-specific Type
Header and Data:
88 06 00 88 5A 5A
Handle 0xD000, DMI type 208, 10 bytes
OEM-specific Type
Header and Data:
D0 0A 00 D0 01 03 FE 00 11 02
Handle 0xD100, DMI type 209, 12 bytes
OEM-specific Type
Header and Data:
D1 0C 00 D1 78 03 07 03 04 0F 80 05
Handle 0xD200, DMI type 210, 12 bytes
OEM-specific Type
Header and Data:
D2 0C 00 D2 F8 03 04 03 06 80 04 05
Handle 0xD201, DMI type 126, 12 bytes
Inactive
Handle 0xD400, DMI type 212, 242 bytes
OEM-specific Type
Header and Data:
D4 F2 00 D4 70 00 71 00 00 10 2D 2E 42 00 11 FE
01 43 00 11 FE 00 0F 00 25 FC 00 10 00 25 FC 01
11 00 25 FC 02 12 00 25 FC 03 00 00 25 F3 00 00
00 25 F3 04 00 00 25 F3 08 00 00 25 F3 0C 07 00
23 8F 00 08 00 23 F3 00 09 00 23 F3 04 0A 00 23
F3 08 0B 00 23 8F 10 0C 00 23 8F 20 0E 00 23 8F
30 0D 00 23 8C 40 A6 00 23 8C 41 A7 00 23 8C 42
05 01 22 FD 02 06 01 22 FD 00 8C 00 22 FE 00 8D
00 22 FE 01 9B 00 25 3F 40 9C 00 25 3F 00 09 01
25 3F 80 A1 00 26 F3 00 A2 00 26 F3 08 A3 00 26
F3 04 9F 00 26 FD 02 A0 00 26 FD 00 9D 00 11 FB
04 9E 00 11 FB 00 54 01 23 7F 00 55 01 23 7F 80
5C 00 78 BF 40 5D 00 78 BF 00 04 80 78 F5 0A 01
A0 78 F5 00 93 00 7B 7F 80 94 00 7B 7F 00 8A 00
37 DF 20 8B 00 37 DF 00 03 C0 67 00 05 FF FF 00
00 00
Handle 0xD401, DMI type 212, 172 bytes
OEM-specific Type
Header and Data:
D4 AC 01 D4 70 00 71 00 03 40 59 6D 2D 00 59 FC
02 2E 00 59 FC 00 6E 00 59 FC 01 E0 01 59 FC 03
28 00 59 3F 00 29 00 59 3F 40 2A 00 59 3F 80 2B
00 5A 00 00 2C 00 5B 00 00 55 00 59 F3 00 6D 00
59 F3 04 8E 00 59 F3 08 8F 00 59 F3 00 00 00 55
FB 04 00 00 55 FB 00 23 00 55 7F 00 22 00 55 7F
80 F5 00 58 BF 40 F6 00 58 BF 00 EB 00 55 FE 00
EA 00 55 FE 01 40 01 54 EF 00 41 01 54 EF 10 ED
00 54 F7 00 F0 00 54 F7 08 4A 01 53 DF 00 4B 01
53 DF 20 4C 01 53 7F 00 4D 01 53 7F 80 68 01 56
BF 00 69 01 56 BF 40 FF FF 00 00 00
Handle 0xD402, DMI type 212, 152 bytes
OEM-specific Type
Header and Data:
D4 98 02 D4 70 00 71 00 00 10 2D 2E 2D 01 21 FE
01 2E 01 21 FE 00 97 00 22 FB 00 98 00 22 FB 04
90 00 11 CF 00 91 00 11 CF 20 92 00 11 CF 10 E2
00 27 7F 00 E3 00 27 7F 80 E4 00 27 BF 00 E5 00
27 BF 40 D1 00 22 7F 80 D2 00 22 7F 00 45 01 22
BF 40 44 01 22 BF 00 36 01 21 F1 06 37 01 21 F1
02 38 01 21 F1 00 39 01 21 F1 04 2B 01 11 7F 80
2C 01 11 7F 00 4E 01 65 CF 00 4F 01 65 CF 10 D4
01 65 F3 00 D5 01 65 F3 04 D2 01 65 FC 00 D3 01
65 FC 01 FF FF 00 00 00
Handle 0xD403, DMI type 212, 157 bytes
OEM-specific Type
Header and Data:
D4 9D 03 D4 70 00 71 00 03 40 59 6D 17 01 52 FE
00 18 01 52 FE 01 19 01 52 FB 00 1A 01 52 FB 04
1B 01 52 FD 00 1C 01 52 FD 02 1D 01 52 F7 00 1E
01 52 F7 08 1F 01 52 EF 00 20 01 52 EF 10 21 01
52 BF 00 22 01 52 BF 40 87 00 59 DF 20 88 00 59
DF 00 E8 01 66 FD 00 E9 01 66 FD 02 02 02 53 BF
00 03 02 53 BF 40 04 02 53 EF 00 05 02 53 EF 10
06 02 66 DF 00 07 02 66 DF 20 08 02 66 EF 00 09
02 66 EF 10 17 02 66 F7 00 18 02 66 F7 08 44 02
52 BF 40 45 02 52 BF 00 FF FF 00 00 00
Handle 0xD800, DMI type 126, 9 bytes
Inactive
Handle 0xDD00, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 00 DD 00 01 00 00 00 10 F5 00 00 00 00 00
00 00 00
Handle 0xDD01, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 01 DD 00 01 00 00 00 11 F5 00 00 00 00 00
00 00 00
Handle 0xDD02, DMI type 221, 19 bytes
OEM-specific Type
Header and Data:
DD 13 02 DD 00 01 00 00 00 12 F5 00 00 00 00 00
00 00 00
Handle 0xDE00, DMI type 222, 16 bytes
OEM-specific Type
Header and Data:
DE 10 00 DE C1 0B 00 00 10 05 19 21 01 00 00 01
Handle 0x7F00, DMI type 127, 4 bytes
End Of Table
Hdparm also does not tell me the max data transfer rate (disk speed) of my current drive although this link : www.wdc.com/en/library/sata/2879-001146.pdf says that it is 3.0Gb/s
and here's hdparm -I /dev/sda
/dev/sda:
ATA device, with non-removable media
Model Number: WDC WD800JD-75JNC0
Firmware Revision: 06.01C06
Standards:
Supported: 6 5 4
Likely used: 8
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
CHS current addressable sectors: 16514064
LBA user addressable sectors: 156250000
Logical/Physical Sector size: 512 bytes
device size with M = 1024*1024: 76293 MBytes
device size with M = 1000*1000: 80000 MBytes (80 GB)
cache/buffer size = 8192 KBytes
Capabilities:
LBA, IORDY(can be disabled)
Standby timer values: spec'd by Standard, with device specific minimum
R/W multiple sector transfer: Max = 16 Current = 8
Recommended acoustic management value: 128, current value: 254
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=120ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* SMART feature set
Security Mode feature set
* Power Management feature set
* Write cache
* Look-ahead
* Host Protected Area feature set
* WRITE_BUFFER command
* READ_BUFFER command
* DOWNLOAD_MICROCODE
SET_MAX security extension
Automatic Acoustic Management feature set
* Device Configuration Overlay feature set
* Mandatory FLUSH_CACHE
* SMART error logging
* SMART self-test
* Gen1 signaling speed (1.5Gb/s)
* Host-initiated interface power management
* SMART Command Transport (SCT) feature set
* SCT Long Sector Access (AC1)
* SCT LBA Segment Access (AC2)
* SCT Error Recovery Control (AC3)
* SCT Features Control (AC4)
* SCT Data Tables (AC5)
Security:
Master password revision code = 65534
supported
not enabled
not locked
frozen
not expired: security count
not supported: enhanced erase
Checksum: correct
Last edited by Inxsible (2011-03-27 04:40:49)

I just checked my BIOS and my current setting is set at IDE although it also mentions that the default should be AHCI. Currently I have a dual boot of Windows 7 (need it for Tax software) and Arch
So I guess, when I get the new HDD, I will first set it to AHCI and then install the OSes on it. See if NCQ helps any, and if not I will turn it back and re-install (if I have to). I am planning to have Windows only in virtualbox in the new drive.
Anyhoo, while I was in the BIOS I found two things which I had questions about :
1) Under Onboard Devices --> Integrated NIC , my setting is currently set at "On w/PXE" and it says the default should be just "On". Would it be ok to change it back to On since its a single machine and its not booting an OS on any server. I just don't want to have to re-install anything now since I will be doing that in the new HDD.
2) How would I know whether my BIOS would support a 64 bit OS in Virtualbox? I checked some setting under Virtualization, but they weren't very clear.
I will edit this post and let you know exactly what settings were present under the Virtualization sub-section.

Init w/o data transfer shows Added/Transfrd - 1/1

Hi ,
Init w/o data transfer load was successful after having applied Note 689964 - ODS object: Switching from a full to delta upload !
I have two weird ( nt sure ) issues below :
Issue 1
On Manage screen I see Added - 1 & Transferred - 1, however I dont see this record in the DSO ( Display data ).
Why is that so ?

Issue 2
All seems green excepting when I go check the Details Tab - I see some reds
DataStore Activation (Change Log) : Errors occurred
No data targets selected for update. Action terminated.
InfoPackage ZPAK_*** could not be started by Bapi_ipak_start
Errors in InfoPackage check for DataStore 0CCA_O09 ; no update possible
Please comment SDNer's

Dear Jr.Roberto,
Issue 1
On Manage screen I see Added - 1 & Transferred - 1, however I dont see this record in the DSO ( Display data ).
Why is that so ?

--> When you do a init with out data transfer, system transfers one record that is not corresponding to the data, but is a control record corresponding to the init selections.
Issue 2
All seems green excepting when I go check the Details Tab - I see some reds
DataStore Activation (Change Log) : Errors occurred
No data targets selected for update. Action terminated.
InfoPackage ZPAK_*** could not be started by Bapi_ipak_start
Errors in InfoPackage check for DataStore 0CCA_O09 ; no update possible
---> It is because you dont have a active update rules maintained for the infosource to the data target, or you have not selected any data target in the infopackage , it can also be the case that the infopackage which generates a program to start the load is having some errors, if possbile create another infopackage and start the load with active Update rules to data target.
Cheers!!!!
Charan
Message was edited by:
Sri Krishna Charan Viswanatha

How to increase AFP data transfer speed?

When I connect to our server from a WAN source outside of our facility the file data transfer rate is extremely slow. We just upgraded to a 10Mps fiber service and that has dematically increased our website data tranfer speed. I would like to find a way to access the file server from remote location and work, but the data transfer rate makes productivity impossible. I would appreciate hearing how other organizations are set-up and functioning with file transfer sizes at an average of 10 to 15 Mb.
Thanks,
Brian
OS10.6.8 Server,

If you don't have enough network bandwidth for your time requirements, you have little chance of success with the direct approach. Techniques such as file compression and such can only provide limited help. If you're transfering multiple copies of the files, then you can push one copy of the file to a hosted provider, and then serve additional copies from there.
As for your network, a ten million bits per second network connection is the speed of first-generation Ethernet. That Ethernet was a fast network, back in 1985. In the era of a one billion bits per second Gigabit Ethernet and increasingly commonly with the ten gigabit Ethernet links, a 10 Mb link is glacial.
A typical DSL network is asymmetric, meaning you'll have 10 Mb down (theoretically) and some fraction of that up. So you might not be getting that 10 Mb in the direction you're coppying files. And this is best case; various of the ISP network links around aren't providing their rated speeds.
AFP stinks on a network, and you're also opening up your file system to remote attackers.
As for WebDAV, read this. In addition to WebDAV, you can also try an sftp or other "simpler" copy command as a test, and see what you get for that. (sftp is also encrypted, which has benefits, though the encryption also requires more processing time.)
But beyond techniques such as data compression (and which may or may not be an option here) or incremental or "delta" changes to the data (which probably isn't an option here) or working locally and batching over the changes, there are few good ways to contend with a too-slow-for-your-needs link.

Question: New Hard Drive and Data Transfer Kit Device

Yep, I go another HDD this time for my lil Compaq Persario 700 series notebook OS Win XP. I bought a DriveWire Univeral Adapter & Data Transfer Kit. I want to know if there would be any issue transferring my iTunes Library to my new HDD? I do have some music apart of my iTunes Library that's DRM protected. Should still deactivate my account during the transfer . . . that is, if it's possible. Thank you for any assistance your can give me. Itunes 10 by the way.

From what you posted, you should be able to set the itunes media folder location to the exHD and then run the ituens consolidate library command.
That will put your itunes library content onto the exHD.
Here's Apple's article on that
http://support.apple.com/kb/ht1364
Pay attention to this note from it
+Note: If you move your library to an external drive, you'll need to power up and connect the drive before starting iTunes. If you don't, iTunes will prompt you to either locate the library or to create a new library (which will result in an empty library). No matter what, it's always a good idea to have a backup of the media you have in iTunes.+
That means you MUST have the exHD connected BEFORe starting itunes. WHat it doesn't mention is, it always needs to have the same drive letter. WIndows can change USB port drive letter without telling you it's doing it. Best practice, is to assign a permanent drive letter such as m: for Media. You can assign drive letters using windows disk manager.
There's no need to deactivate any account during this procedure - why do you think you should?

Flat File loading Initialize with out Data transfer is disabled in BI 7.0

Hi experts,
When loading through flat file in BI 7.0 for Info Package Level Initialization Delta Process with data Transfer is coming by default,but when i want to select Initialization Delta Process without Data transfer is disabled. (in the creation of Data Source (flat file) in the Extraction Tab Delta Process is changed to FIL1 Delta Data (Delta Images).
please provide me Solution.
regards
Subba reddy.

Hi Shubha,
For flat file load please go throught he following link:
http://help.sap.com/saphelp_nw70/helpdata/EN/43/03450525ee517be10000000a1553f6/frameset.htm
This will help.
Regards,
Mahesh

Rp-pppoe connected but no data transfer

hi,
i installed arch on 27th . Post installation i setup internet connection using rp-pppoe, which was a straight forward setup. I also got connected to net and downloaded data upon a system upgrade. Except this one instance, thereafter last two days if connected i am getting no data transfer after a connection is established.
Upon ping of 8.8.8.8 i am getting this error of destination net unreachable & if you ping google.com i get the error unknown host.
when i checked the pppoe status i get this message:
link is up and running on interface ppp0 and no packet errors both RX and TX.
The system upgrade did not happen on 27th due to the TZselec tconflicting files error.
It is a fresh system.
i am pasting below the lines from the messages.log of 27th when i got the data transfer happened for the first time and next of 29th with the same system but nothing happening except i am connected.
27th:
Jun 27 12:46:03 localhost kernel: [ 117.794497] r8169 0000:02:00.0: eth0: link up
Jun 27 12:46:06 localhost kernel: [ 120.763326] eth0: no IPv6 routers present
Jun 27 12:58:01 localhost kernel: [ 835.641169] PPP generic driver version 2.4.2
Jun 27 12:58:01 localhost pppd[888]: pppd 2.4.5 started by root, uid 0
Jun 27 12:58:01 localhost pppd[888]: Using interface ppp0
Jun 27 12:58:01 localhost pppd[888]: Connect: ppp0 <--> /dev/pts/0
Jun 27 12:58:02 localhost pppoe[889]: PADS: Service-Name: ''
Jun 27 12:58:02 localhost pppoe[889]: PPP session is 14295 (0x37d7)
Jun 27 12:58:02 localhost pppd[888]: CHAP authentication succeeded: CHAP authentication success, unit 7436
Jun 27 12:58:02 localhost pppd[888]: CHAP authentication succeeded
Jun 27 12:58:02 localhost kernel: [ 837.068606] PPP BSD Compression module registered
Jun 27 12:58:03 localhost pppd[888]: Cannot determine ethernet address for proxy ARP
Jun 27 12:58:03 localhost pppd[888]: local IP address 117.204.173.123
Jun 27 12:58:03 localhost pppd[888]: remote IP address 117.204.160.1
Jun 27 12:58:03 localhost pppd[888]: primary DNS address 218.248.255.212
Jun 27 12:58:03 localhost pppd[888]: secondary DNS address 218.248.241.2
Jun 27 13:01:01 localhost /USR/SBIN/CROND[934]: (root) CMD (run-parts /etc/cron.hourly)
Jun 27 13:01:01 localhost anacron[938]: Anacron started on 2012-06-27
Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.daily' in 28 min.
Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.weekly' in 48 min.
Jun 27 13:01:01 localhost anacron[938]: Will run job `cron.monthly' in 68 min.
Jun 27 13:01:01 localhost anacron[938]: Jobs will be executed sequentially
Jun 27 13:04:10 localhost -- MARK --
Jun 27 13:16:48 localhost pppoe-stop: Killing pppd
Jun 27 13:16:48 localhost pppd[888]: Terminating on signal 15
Jun 27 13:16:48 localhost pppd[888]: Connect time 18.8 minutes.
Jun 27 13:16:48 localhost pppd[888]: Sent 411268 bytes, received 16885685 bytes.
29th :
Jun 29 17:54:13 localhost kernel: [ 5.019108] r8169 0000:02:00.0: eth0: link down
Jun 29 17:54:14 localhost dhcpcd[675]: eth0: carrier acquired
Jun 29 17:54:14 localhost kernel: [ 6.632983] r8169 0000:02:00.0: eth0: link up
Jun 29 17:54:14 localhost dhcpcd[675]: eth0: broadcasting for a lease
Jun 29 17:54:15 localhost dhcpcd[675]: eth0: offered 192.168.1.2 from 192.168.1.1
Jun 29 17:54:15 localhost dhcpcd[675]: eth0: acknowledged 192.168.1.2 from 192.168.1.1
Jun 29 17:54:15 localhost dhcpcd[675]: eth0: checking for 192.168.1.2
Jun 29 17:54:21 localhost dhcpcd[675]: eth0: leased 192.168.1.2 for 10080 seconds
Jun 29 17:54:21 localhost dhcpcd[675]: forked to background, child pid 702
Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) STARTUP (1.4.8)
Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) INFO (Syslog will be used instead of sendmail.): No such file or directory
Jun 29 17:54:21 localhost /usr/sbin/crond[751]: (CRON) INFO (running with inotify support)
Jun 29 17:54:47 localhost kernel: [ 39.424170] NET: Registered protocol family 10
Jun 29 17:54:47 localhost kernel: [ 39.441086] NET: Registered protocol family 4
Jun 29 17:54:47 localhost kernel: [ 39.458946] NET: Registered protocol family 5
Jun 29 17:54:47 localhost kernel: [ 39.480053] PPP generic driver version 2.4.2
Jun 29 17:54:47 localhost pppd[811]: pppd 2.4.5 started by root, uid 0
Jun 29 17:54:47 localhost pppd[811]: Using interface ppp0
Jun 29 17:54:47 localhost pppd[811]: Connect: ppp0 <--> /dev/pts/0
Jun 29 17:54:48 localhost pppoe[812]: PADS: Service-Name: ''
Jun 29 17:54:48 localhost pppoe[812]: PPP session is 2021 (0x7e5)
Jun 29 17:54:48 localhost pppd[811]: CHAP authentication succeeded: CHAP authentication success, unit 4257
Jun 29 17:54:48 localhost pppd[811]: CHAP authentication succeeded
Jun 29 17:54:48 localhost kernel: [ 40.866233] PPP BSD Compression module registered
Jun 29 17:54:48 localhost pppd[811]: not replacing existing default route via 192.168.1.1
Jun 29 17:54:48 localhost pppd[811]: Cannot determine ethernet address for proxy ARP
Jun 29 17:54:48 localhost pppd[811]: local IP address 117.204.161.173
Jun 29 17:54:48 localhost pppd[811]: remote IP address 117.204.160.1
Jun 29 17:54:48 localhost pppd[811]: primary DNS address 218.248.255.212
Jun 29 17:54:48 localhost pppd[811]: secondary DNS address 218.248.241.2
Jun 29 17:54:57 localhost kernel: [ 49.523342] eth0: no IPv6 routers present
Jun 29 18:01:01 localhost /USR/SBIN/CROND[876]: (root) CMD (run-parts /etc/cron.hourly)
Jun 29 18:01:01 localhost anacron[881]: Anacron started on 2012-06-29
Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.daily' in 29 min.
Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.weekly' in 49 min.
Jun 29 18:01:01 localhost anacron[881]: Will run job `cron.monthly' in 69 min.
Jun 29 18:01:01 localhost anacron[881]: Jobs will be executed sequentially
Jun 29 18:04:04 localhost pppoe-stop: Killing pppd
Jun 29 18:04:04 localhost pppd[811]: Terminating on signal 15
Jun 29 18:04:04 localhost pppd[811]: Connect time 9.3 minutes.
Jun 29 18:04:04 localhost pppd[811]: Sent 0 bytes, received 926 bytes.
Now in both the cases i got connected but as i said before except twice on 27th i am not able to have data transfer of any type either through ping or pacman upgrade.
Upon the same time i cross checked on my other systems, ubuntu and windows and i had no problems with the same, to confirm any issue with my isp. As of now i am typing one of those systems only.
I have googled a lot, read the other options of pppd,etc, but upon similar queries by other users found no viable solution to this problem.
My hostname is also proper in the config files. I also once used static ip for a change to see if things go working
but nothing is sucessful so far.
The only viable solution i read so far upon google search where there was a success was a fresh installation of arch by an user and he got the same working. But definitely i wont go with that. As i said above i got connected twice on the day of the installation and post that also i am now getting connected but with no data transfer.
Pls suggest what to do to get the connection working.
regards

Upon a search on the forums yesterday
i read one user query on this forums who was advised the same and he had the same problem like me and it did not got solved with either methodds.
Last his query was still open. I did not save that link.
So i did not give that method a try so far, waiting for a solution for this method without going for new developments thinking a search for a day or two might get some viable results.
i guess you are mentioning the topic of this link
https://wiki.archlinux.org/index.php/Pppd [This article explains how to set up a point-ti-point connections using pppd and the kernel PPPoE driver. ]
Further in my case the connection is happening and also getting disconnected. You can very well see the same in the log file which i pasted.
Jun 27 13:16:48 localhost pppd[888]: Connect time 18.8 minutes.
Jun 27 13:16:48 localhost pppd[888]: Sent 411268 bytes, received 16885685 bytes.
Jun 29 18:04:04 localhost pppd[811]: Connect time 9.3 minutes.
Jun 29 18:04:04 localhost pppd[811]: Sent 0 bytes, received 926 bytes.
So same thing but different results on 2 different days. So what the problem really is i dont understand. Infact what the problem is the system is also not giving out, except that a connection happens, no data transfer takes place and the connection is cut and the stats are also show. Just diving to implement some new method or a reinstall, without resolving this which looks sensible yet senseless too, simply does not appeal here. If really there is some bug or issue with that rp-pppoe package then there is some point to jump to another method.
This must be solvable some way or other.
Last edited by beopen (2012-06-29 17:30:16)

Hard Drive Data Transfer rate setting

I am looking at upgrading my MacBook hard drive, but the drive I wanted to get is SATA-300, and I want to set the data transfer speed to 150 MB/sec to reduce the power draw of the drive without changing performance much. I know in Windows you can do this in to BIOS settings. Does anyone know how I would do this in Leopard? I assume it would be Terminal commands.

As far as I know, they were just talking about Laptop drives only. It was a great article with lots of detail.
I am trying to find the article I read on setting BIOS, but pages that carry the info on Laptop power consumption that I was reading were...
http://www.tomshardware.com/2008/02/18/wdand_toshiba_join_theclub/page2.html
http://www.tomshardware.com/2008/01/24/hdd_galore/page4.html
http://www.tomshardware.co.uk/Notebook-harddrive,review-2376-3.html

Re: (forte-users) Delays in data transfer..server-to-client

I would try using DOM (distributed object manager) traces. trc:do:20 will
give you information on each messages sent from and received by the
partition. Levels are 1, 2, 5, 7, and 8, and trc:do:*:8 is very
verbose. trc:do:20:1 may tell you what you want to know. trc:do:1:1 will
give you a basic 1-line-per DOM event trace that may also be all you need.
Communications manager traces will tell you about network and socket-level
activity, but not about the sizes of the messages themselves. In addition,
the operating system makes decisions about physical packet size and
send/receive timing, so CM activities only generally map to actual network
activity.
-tdc
iPlanet Integration Server Engineering
At 09:24 AM 5/1/01 -0700, you wrote:
All,
We are experiencing delays in object transfer between server and client. The
delays are longer with large objects (a single object with an array of objects
that reflect the rows returned in a database) than small (ie: 10 rows vs 400).
Does anyone have any (actual) experience using the various Forte' flags in
order
to show the actual size of the object/packets being passed between the server
and client?
We are using input/output between client and server, input on all the SO's
within a partition. Response on the server side is good, roughly 6 seconds or
so. The round trip fare however from the time the client makes the SO call to
the time that it completes is in the 25-30 second range, leaving roughly 20-25
seconds unaccounted for. I have brought in the network guys who are
requesting
the data size and packet information. I did not see what I am looking for
using
the trc:cm:*:4 and trc:cm:*:8 flags. I will be trying the trc:cm:*:10
flag, but
Forte' indicates that this flag is very verbose, the systems group hates
it when
I use up all of THEIR disk space!
Any ideas would be appreciated as always.

Jeff,
If the object you are passing does not require changes made to it in the
server partition to be returned, pass the object as copy input (pass by
value not reference). If it is necessary to pass the object as input, try
to pass only the attributes that are required to the remote partition
instead of the whole object.
Input/Output is normaly used with scalar variables. When a scalar is passed
to a remote partition, if the value is changed in that partition, the value
is not returned to the calling partition unless Input/Output is used.
Input/Output should not be used for object type parameters, if you need to
pass a reference, use Input only. If you can pass by value, use Copy Input.
You will notice a huge difference in performance changing from Input to Copy
input when passing large objects.
Hope this helps,
Travis Foote
Fortedeveloper.com Inc.
----- Original Message -----
From: "Jeff Bennett" <[email protected]>
To: <[email protected]>
Sent: Tuesday, May 01, 2001 9:24 AM
Subject: (forte-users) Delays in data transfer.. server-to-client
>
All,
We are experiencing delays in object transfer between server and client.The
delays are longer with large objects (a single object with an array ofobjects
that reflect the rows returned in a database) than small (ie: 10 rows vs400).
>
Does anyone have any (actual) experience using the various Forte' flags inorder
to show the actual size of the object/packets being passed between theserver
and client?
We are using input/output between client and server, input on all the SO's
within a partition. Response on the server side is good, roughly 6seconds or
so. The round trip fare however from the time the client makes the SOcall to
the time that it completes is in the 25-30 second range, leaving roughly20-25
seconds unaccounted for. I have brought in the network guys who arerequesting
the data size and packet information. I did not see what I am looking forusing
the trc:cm:*:4 and trc:cm:*:8 flags. I will be trying the trc:cm:*:10flag, but
Forte' indicates that this flag is very verbose, the systems group hatesit when
I use up all of THEIR disk space!
Any ideas would be appreciated as always.
-jeff
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: [email protected]

N95 8GB reboots periodically in data transfer mode

I have a new N95 8GB running firmware v20. Unfortunately, when I use the genuine USB cable and select "Data Transfer Mode" the phone reboots 60 seconds after I connect the cable (and thereafter each 60 seconds when I don't touch the phone).
I have tried with a non-genuine cable and the behaviour is the same.
Coincidentally the "Power Save Time-out" is set to 60 seconds. When I change this to another value, say 40 seconds, then the above rebooting happens every 40 seconds.
This appears to be a phone bug and makes it extremely difficult to use data transfer mode, unless you can transfer files within the power save time-out period, or unless you are prepared to press a button on the phone within this period.
**Nokia please fix this**
See related post: /discussions/board/message?board.id=smartphones&thread.id=81967&view=by_date_ascending&page=1

Well,rotateme works perfectly for me and i have a n95 8gb too.So there are two things that might happening.
1.You are doing something wrong with the whole installation(does rotateme works when you install it?)
2.You downloaded your self a corrapted or somekind of a virus or a bug .sis file and installed it to your phone.
Why dont you try to download one other rotateme file for you?You can find plenty rotateme from a lot of users.I can send you mine,if you want send me an e-mail and i`ll send to you the .sis file that i used and as i said,it works fine for me.
Peace
Message Edited by noslien on 06-Feb-2008 07:47 AM
Eykleidis

Field symbols not working in data transfer VOFM routine

Hi,
I have been trying to set a value using field symbols, however for some reasons its not working. I am using a field symbol in a data transfer routine and the value which I am trying to set is a standard field outside the VOFM routine code.
I am trying to set a field gla_subrc which is actually a changing parameter.
The actual paramter is gn_subrc of type sy-subrc and within the form the name is gla_subrc. I need to set this changing parameter gla_subrc using the data transfer routine.
Is there a specific rule that field symbols dont work for changing paramters within subroutine or is there a specific syntax.
The syntax I am using is
ASSIGN ('(SAPLV50S)gla_subrc') to <fs>.
I also used the local program name instead of main program but still that does not work. Tried using the actual parameter as well.
Can someone please help me in this.
Thanks & Regards,
Naresh.

I need to stop outbound delivery creation against STO using vl10b transaction. The only way to stop creation is using data transfer delivery VOFM routine.
If i give an error message MESSAGE E001, this will give a hard error which is not acceptable. To avoid this, i use a perform message statment with message id and certain parameters which can displayed in a log.
However to make sure this message is displayed in log, I am clearing a work area having specific data needed for delivery creation.
Because of this clear, my error message gets captured in log but along with this another fake message is displayed in log which caused by the clear message.
The user gets confused as he now sees 2 messages, 1 which is correct and other 1 which is fake and that confuses him.
Data transfer routine is not the best place to give messages in log but we have very few options. The only way the system can give 1 message is if i set gla_subrc to 1. This is a variable which will help the system understand that the delivery should not be created as there is something wrong because the value is 1. Hence it will stop the creation and instead display whatever message i had passed to the log.
I need to somehow set this variable to 1 based on lot of analysis that has been done in the past.
Please let me know if there is any way by which we can fix this.
Thanks & Regards,
Naresh.

Journal entries in Data Transfer workbench

Hi all
When I try to Upload journal entries with debits and credits using data transfer workbench I get an error says Unbalanced transaction.
I tried lot of things to change but still no go.
can someone guide me with this data migration
thanks
vinodh kumar

paste it in note pad and save this sample and open with excel
RecordKey     LineNum     AccountCode     AdditionalReference     BaseSum     ContraAccount     CostingCode     Credit     Debit     DueDate     FCCredit     FCCurrency     FCDebit     GrossValue     LineMemo     ProfitCode     ProjectCode     Reference1     Reference2     ReferenceDate1     ReferenceDate2     ShortName     SystemBaseAmount     SystemVatAmount     TaxDate     TaxGroup     VatAmount     VatDate     VatLine
RecordKey     LineNum     AccountCode     AdditionalReference     BaseSum     ContraAccount     CostingCode     Credit     Debit     DueDate     FCCredit     FCCurrency     FCDebit     GrossValue     LineMemo     ProfitCode     ProjectCode     Reference1     Reference2     ReferenceDate1     ReferenceDate2     ShortName     SystemBaseAmount     SystemVatAmount     TaxDate     TaxGroup     VatAmount     VatDate     VatLine
1     1     110001                              28059     30.01.2009                                        abc pte ltd     abc pte ltd     31.01.2009          110001               30.01.2009
2     2     110002                              50000     23.01.2009                                        abc pte ltd     abc pte ltd     31.01.2009          110002               23.01.2009
3     3     261001                         28059          23.01.2009                                        abc pte ltd     abc pte ltd     31.01.2009          261001               23.01.2009
4     4     261001                         50000          22.01.2009                                        abc pte ltd     abc pte ltd     31.01.2009          261001               22.01.2009
Edited by: Vinod Kumar on Jul 28, 2009 6:56 AM

License server in data transfer workbench

Dear All Experts/Gurus,
I have a problem about log on to data transfer workbench (DTW). I don't understand why I must put numbers in license server field before log on to Data transfer workbench ? In the license server field of license administration form, I've seen the license server is words for example jimmymc, then beside it 40000.
I log on DTW, I fill jimmymc in the license server field but I've got error message:
"connection to jimmymc has failed. Error code 100000001. Connection with license server failed"
I don't understand why it succeeds if I fill numbers for example 130.1.2.5:40000, it works successful. What actually the function of license server field ? why could it be different with license server in the license administration form ?
I apreciate your answer. TIA
Rgds,

Jimmy,
The net-net is that ... the way you log into the DTW as of the 2005A version is different becasue the overall licensing mechanism used by SAP Business One for 2005 changed from what was used in version 2004. The licensing mechanism now uses CORBA. This allows connection without having to have an IP Address, but you can still use one as you have seen. When you install the License Server for Business One, the default connection "port" used and is defaulted to in the License Server is 30000 ... although you can change this to any port not being used. Again ... the net-net is that is how it works and that is what is now required for connection or use the IP.
HTH,
Eddy

Change data transfer

Similar Messages

Maybe you are looking for