Abstract: Aspects of the invention include systems and methods configured to efficiently evaluate the efforts of a code migration (e.g., porting task) between different platforms. A non-limiting example computer-implemented method includes receiving a function of a source platform. The function can include a plurality of fields. An initial vector is constructed for each of the plurality of fields. The initial vector encodes a value of the respective field according to an encoding rule. The initial vectors are merged into a single final vector and the final vector is classified into one of a plurality of system function families of the source platform. A vector of a target platform at a minimum distance to the final vector is identified and an assessment is provided that includes a difficulty in porting a project comprising the function between the source platform and the target platform based at least in part on the minimum distance.

Abstract: Embodiments relate to methods, systems, and computer program products for path management in a processing system. In a method, in response to receiving a request for adding a target controlling unit into a processing system, a plurality of network nodes in the processing system are divided into a group of subnets based on a topology of the plurality of network nodes, the plurality of network nodes being connected to at least one controlling unit in the processing system. A workload estimation is determined, the workload estimation representing a workload to be caused by the target controlling unit to the processing system. A target subnet is selected from the group of subnets for connecting the target controlling unit into the processing system based on the workload estimation. With these embodiments, the target subnet may be selected in an automatic way such that the performance of the processing system may be increased.

Abstract: Aspects of the invention include systems and methods configured to efficiently evaluate the efforts of a code migration (e.g., porting task) between different platforms. A non-limiting example computer-implemented method includes receiving a function of a source platform. The function can include a plurality of fields. An initial vector is constructed for each of the plurality of fields. The initial vector encodes a value of the respective field according to an encoding rule. The initial vectors are merged into a single final vector and the final vector is classified into one of a plurality of system function families of the source platform. A vector of a target platform at a minimum distance to the final vector is identified and an assessment is provided that includes a difficulty in porting a project comprising the function between the source platform and the target platform based at least in part on the minimum distance.

Abstract: Sensitive data is protected in a software product. A source file of the software product is compiled to generate an object file, in which the source file includes at least one piece of sensitive data marked with a specific identifier. The object file has a secure data section for saving storage information of the at least one piece of sensitive data at compile-time and run-time. The object file is linked to generate an executable file. The executable file updates the secure data section at run-time. Sensitive data is also protected when a core dump is generated.

Abstract: The present invention provides a computer implemented method, system, and computer program product for monitoring a ticket, the method including receiving credentials by a processing unit from a device via manual presentation of the device to a manual sensor logically coupled to the processing unit, generating a ticket identifier (ID) based on the credentials, transmitting the ticket ID from the processing unit to the device, establishing a wireless connection between the device and the processing unit, checking the wireless connection before each occurrence of an event, checking the wireless connection after each occurrence of the event, and updating a status of a ticket in light of the checking. In an exemplary embodiment, a ticket system includes a processing unit, a manual sensor, a wireless sensor, and a device, where the processing unit transmits the ticket ID, and where the processing unit verifies continued connection at key events.

Abstract: Sensitive data is protected in a software product. A source file of the software product is compiled to generate an object file, in which the source file includes at least one piece of sensitive data marked with a specific identifier. The object file has a secure data section for saving storage information of the at least one piece of sensitive data at compile-time and run-time. The object file is linked to generate an executable file. The executable file updates the secure data section at run-time. Sensitive data is also protected when a core dump is generated.

Abstract: Sensitive data is protected in a software product. A source file of the software product is compiled to generate an object file, in which the source file includes at least one piece of sensitive data marked with a specific identifier. The object file has a secure data section for saving storage information of the at least one piece of sensitive data at compile-time and run-time. The object file is linked to generate an executable file. The executable file updates the secure data section at run-time. Sensitive data is also protected when a core dump is generated.

Abstract: The present invention provides a computer implemented method, system, and computer program product for monitoring a ticket, the method including receiving credentials by a processing unit from a device via manual presentation of the device to a manual sensor logically coupled to the processing unit, generating a ticket identifier (ID) based on the credentials, transmitting the ticket ID from the processing unit to the device, establishing a wireless connection between the device and the processing unit, checking the wireless connection before each occurrence of an event, checking the wireless connection after each occurrence of the event, and updating a status of a ticket in light of the checking. In an exemplary embodiment, a ticket system includes a processing unit, a manual sensor, a wireless sensor, and a device, where the processing unit transmits the ticket ID, and where the processing unit verifies continued connection at key events.

Abstract: The present invention provides a computer implemented method, system, and computer program product for monitoring a ticket, the method including receiving credentials by a processing unit from a device via manual presentation of the device to a manual sensor logically coupled to the processing unit, generating a ticket identifier (ID) based on the credentials, transmitting the ticket ID from the processing unit to the device, establishing a wireless connection between the device and the processing unit, checking the wireless connection before each occurrence of an event, checking the wireless connection after each occurrence of the event, and updating a status of a ticket in light of the checking. In an exemplary embodiment, a ticket system includes a processing unit, a manual sensor, a wireless sensor, and a device, where the processing unit transmits the ticket ID, and where the processing unit verifies continued connection at key events.

Abstract: Sensitive data is protected in a software product. A source file of the software product is compiled to generate an object file, in which the source file includes at least one piece of sensitive data marked with a specific identifier. The object file has a secure data section for saving storage information of the at least one piece of sensitive data at compile-time and run-time. The object file is linked to generate an executable file. The executable file updates the secure data section at run-time. Sensitive data is also protected when a core dump is generated.

Abstract: Sensitive data is protected in a software product. A source file of the software product is compiled to generate an object file, in which the source file includes at least one piece of sensitive data marked with a specific identifier. The object file has a secure data section for saving storage information of the at least one piece of sensitive data at compile-time and run-time. The object file is linked to generate an executable file. The executable file updates the secure data section at run-time. Sensitive data is also protected when a core dump is generated.

Abstract: Sensitive data is protected in a software product. A source file of the software product is compiled to generate an object file, in which the source file includes at least one piece of sensitive data marked with a specific identifier. The object file has a secure data section for saving storage information of the at least one piece of sensitive data at compile-time and run-time. The object file is linked to generate an executable file. The executable file updates the secure data section at run-time. Sensitive data is also protected when a core dump is generated.